A truly fantastic package idea! Thanks a lot for sharing it.
I just wish it would be cut a little bit differently.
1 module for the formats using only the stdlib
1 module each for sqlite and excel support.
That woukd allow better control over dependencies
and allow me to avoid the cgo depen
You could use the Go module support to tie the cli version to the version of
your cli module.
The module version can now be optained from the binary via
https://godoc.org/runtime/debug#ReadBuildInfo and then in
BuildInfo.Module.Version field.
Since that is part of the official Go std-library,
I can only recommend
https://pkg.go.dev/golang.org/x/oauth2/clientcredentials?tab=doc if you are
implementing that.
Configure clientcredentials.Config and use the http.Client returned by the
Client method of that Config to do all your http calls.
It manages all the token refreshing automatical
Hi everyone,
does someone has experience with causal profiling in Go? (see
http://www.sigops.org/sosp/sosp15/current/2015-Monterey/printable/090-curtsinger.pdf
if you are not aware of that topic)
Please note that I am aware of https://morsmachine.dk/causalprof but I want to
hear a few more op
https://tech.townsourced.com/post/embedding-static-files-in-go/ is a great
article comparing multiple asset embedding solutions.
You may come to different conclusion than the author depending on your own
tradeoffs, but I found the comparison table very useful for making those
decisions myself.
https://godoc.org/golang.org/x/image/math/fixed might provide some hints how to
work with this kind of type.
The idea is to use a special type and provide all operations you need.
https://godoc.org/math/big#Rat might be helpful to create first tests of the
basic math operations with maximum pre
Hi Michael,
while I understand that you are having fun with the pytogo translator, please
note that a base36 encoder is already part of the Go stdlib
Namely https://golang.org/pkg/math/big/#Int.Text supports a base of 36 for big
integers and https://golang.org/pkg/strconv/#FormatInt supports ba
I would suggest opening an issue for that, if it isn't.
A runtime provided profile similar to the contention profile might be very
useful here.
But that needs careful design.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe fro
You seem to ignore the error from out.Close()
What is out.Close reporting after the io.Copy?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubsc
You might be interested in https://gohugo.io/overview/introduction/ to get
some inspiration or take a peek when you are stuck.
On Monday, July 10, 2017 at 3:31:10 AM UTC+2, Oliver Steele wrote:
>
> Hi everyone,
>
> As my "learn Go" project, I've been working on a clone of the Jekyll
> static sit
I love the idea and it is a really great service to the community.
What I am asking myself:
Why couldn't I use the standard Go benchmark interface defined in
https://godoc.org/testing ? This would allow me to quickly share any benchmark
I did write already.
Where can I see what machine and go
Thx for the valuable feedback!
I just added a bugs section to the package doc so it's transparent, that the
same limitations (and workarounds) apply as in the sync/atomic package.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe
Hi all,
I wrote a small package which implements atomic operations on types.
This is more comfortable to use and enabled building an atomic boolean type
(which has been the motivation) here.
Documentation at https://godoc.org/github.com/nightlyone/atomic
Source code at: https://github.com/night
What checks are you doing on struct field names and tags? That will be crucial
to answering your question.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang
Sponsor a meetup nearby. Or help them with a venue or catering. Speak on a
local conference or meetup about how Go has been key to your success to
encourage others to pursue their dreams. Make a workshop for newbies in your
area.
Happy donating.
--
You received this message because you are su
Are you looking for something like
https://godoc.org/github.com/nightlyone/lockfile ?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@goo
let me know if you have any other questions.
>
> Best regards,
>
> Marcel
>
>
> On Wed, Sep 21, 2016 at 5:41 AM, Nigel Tao > wrote:
>
>> On Wed, Sep 21, 2016 at 7:34 AM, 'Ingo Oeser' via golang-nuts
>> > wrote:
>> > I am pretty sure I
The default of using only one thread to run goroutines default changed with Go
1.5 to using all available cores reported by the OS. Tuning GOMAXPROCS has now
less relevance in practice, rendering the article as outdated in that regard.
Just leave the GOMAXPROCS settings alone until a strong use
Thanks for the suggestion, but I am looking for an implementation of
http://unicode.org/reports/tr29/
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts
Hi all,
I am pretty sure I am overlooking something in the repository
https://godoc.org/golang.org/x/text but I cannot find something to split text
into words according to the next Unicode word splitting algorithm.
Has anyone examples or can point me to the right direction? Can anyone confirm
The missing inclusion stems from a misunderstanding of the intended api.
The Size method should return the upper bound for the offset passed to ReadAt
known ahead of time.
If the upper bound cannot be detected, the SizedReaderAt will simply fail
creation.
When the Size changes, ReadAt will r
Hi fellow gophers,
there is an issue opened by myself at
https://github.com/golang/go/issues/14255
where I suggested adding a bit of guidance on using
x := new(MyStruct) vs. x := &MyStruct{}
Please vote using the reaction feature of github, whether you agree (thumbs
up) or disagree (thumbs
Please note that there is no concept central repository of Go code. Those
questions in the survey are very confusing for a Go developer. Maybe you could
exclude those questions for Go developers. Otherwise you would need to ignore
the results for Go developers here in your later analysis.
--
Y
Could you document your workaround here?
It might be needed by others for the next 6 months because the bug has been
classified as Go 1.8 work.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving e
24 matches
Mail list logo