> Is this simply a recommendation or should the docs be updated to clarify what
> this means?
perhaps the latter, although that question only seems to come up once
every two or so years. here's a good link:
https://groups.google.com/d/msg/golang-nuts/XqW1qcuZgKg/Ui3nQkeLV80J
the entire
>> fmt.Formatter is woefully under documented.
>
> My reference is pkg/errros -
> https://github.com/pkg/errors/blob/master/errors.go#L127
we have wasted tens of man-hours hunting for a bug that didn't
manifest in logs due to that custom formatter. %#v basically went
directly to stringer without
Hi,
I have a non-profit I'd like to support. Who do I ask to put a banner
on golang.org for me?
(reductio ad absurdum)
On Sun, Jun 14, 2020 at 4:08 PM Robert Engels wrote:
>
> Equating not supporting this and supporting marginalized groups is not
> correct. You can support marginalized groups
> Cool, makes sense. Assuming NewTicker does return monotonic time.
>
> I wonder if there is a way to verify.
just fmt.Println the value you receive on the ticker chan, you'll see
the monotonic component tacked on in the end:
$ cat t.go
package main
import (
"fmt"
"time"
)
func main() {
> Does anyone know if the time data that NewTicker returns (i.e. via it's
> channel, etc...) includes monotonic time?
it's right at the top: https://golang.org/pkg/time/
On Wed, Jun 10, 2020 at 4:48 PM Curtis Paul wrote:
>
> It sounds like NewTicker will dynamically adjust to keep tick time
thanks. that ought to do it.
On Fri, May 1, 2020 at 11:16 AM Brian Candler wrote:
>
> parseIP returns a net.IP which is just a slice of bytes without the zone.
>
> However, type net.IPAddr includes the zone. Looks like net.ResolveIPAddr
> will do the job:
>
>
IPv6 addresses including a zone identifier [rfc4007] are not parsed
correctly by net.ParseIP. is there any point in creating an issue or
is this intentional and we're supposed to strip the zone identifier?
https://play.golang.org/p/kQKyYYnZydX
--
You received this message because you are
to avoid allocations you have to hint at the type of what you're going
to print. for example see/use zerolog: https://github.com/rs/zerolog
On Mon, Mar 9, 2020 at 10:36 AM 'Axel Wagner' via golang-nuts
wrote:
>
> IMO, there really isn't a super good answer. The simple answer is: You need
> to
my take:
- c++ programmers are going to c++ program. film at 11 (rob pike had a
talk about that)
- dart has UI
- rust is fashionable, but scary (if you've done rust you'll know why)
yes, go was touted as a systems programming language, but it meant
"distributed systems". had that been made clear
got it down to two:
https://play.golang.org/p/jmTqhLGaLY_T
On Fri, Feb 21, 2020 at 11:24 AM Bruno Albuquerque wrote:
>
> This is interesting. If I simplify the loop to something like this:
>
> nrgbaData := make([]byte, len(rgbData)+(len(rgbData)/3))
>
> _ = nrgbaData[len(rgbData)]
>
>
?w=1 is an option.
On Tue, Feb 18, 2020 at 7:16 PM Wojciech S. Czarnecki wrote:
>
> Dnia 2020-02-18, o godz. 10:16:57
> Manlio Perillo napisał(a):
>
> > Here is an example of a diff with a lot of noise, where the actual change
> > is very hard to see:
> >
sorry, wanted to add: submit your file to VT and see if it triggers a
detection there (like in my link it is most likely that only the MS
engine will detect it). then you have a case to argue.
On Tue, Feb 11, 2020 at 9:29 PM andrey mirtchovski
wrote:
>
> you can find similar dete
you can find similar detections on virustotal. unfortunately it looks
like a false positive:
https://www.virustotal.com/gui/file/93eb448cedd4b4355065a4f9193d8548b02bc56ed5ba9e774095f9ab3da46227/detection
there are members of this community working for microsoft, perhaps
they'll have an avenue
i would strongly advise against implementing advice received online
for something as important as auth. my suggestion is to work with curl
from the command line (examples are given on the webpage you linked)
until you have the process working. implementing that afterwards using
http.Client will be
sorry, i meant to put this in too;
https://play.golang.org/p/vn5iMAWbDiv
On Fri, Jan 3, 2020 at 11:27 AM andrey mirtchovski
wrote:
>
> https://play.golang.org/p/cpKEQZJKDsh
>
> On Fri, Jan 3, 2020 at 11:24 AM X-Thief wrote:
> >
> > thx but have you tried it
https://play.golang.org/p/cpKEQZJKDsh
On Fri, Jan 3, 2020 at 11:24 AM X-Thief wrote:
>
> thx but have you tried it? it just gives positive on playground.
>
> пятница, 3 января 2020 г., 22:05:48 UTC+4 пользователь Ian Lance Taylor
> написал:
>>
>> On Fri, Jan 3, 2020 at 9:50 AM X-Thief wrote:
You'll need to create a FlagSet instead and pass ContinueOnError as
the error handling. If .Parse() returns an error call
.PrintDefaults(), then print the error.
On Sun, Dec 8, 2019 at 4:00 AM Thomas Nyberg wrote:
>
> Hello,
>
> Given the following file `flag_example.go`:
>
> package main
>
>
this is quickly becoming off-topic. however, from
https://en.wikipedia.org/wiki/Geographical_centre:
"As noted in a USGS document "There is no generally accepted
definition of geographic center, and no completely satisfactory method
for determining it."[1]
In general, there is room for debate
it once for callbacks in a
library in 2013 and forgot about it :) it just works.
On Thu, Dec 5, 2019 at 9:52 PM Dan Kortschak wrote:
>
> Thanks. Can you explain the reason for this so it sticks in my head?
>
> On Thu, 2019-12-05 at 21:03 -0700, andrey mirtchovski wrote:
> > you
you just need to split it in two files. the cfuncs go into another
(sorry for lack of playground link):
$ go build cgo.go cfunc.go
$ ./cgo
Hello from stdio
$ cat cgo.go
package main
/*
#include
extern void myprint(char *s);
*/
import "C"
import "unsafe"
//export Example
func Example() {
cs
i think JuciÊ wants us to crack the md5. i'm fresh off a CTF
competition so i don't have any more resources to throw at warming the
universe and increasing entropy, unfortunately...
On Sat, Nov 30, 2019 at 6:43 PM Michael Jones wrote:
>
>
> My answer is this place.
> 14°35'03.5"S 53°03'51.3"W
>
>> I think it only catches concurrent access to the same address, so not sure
>> if it catches everything.
>
>
> If two things aren't writing concurrently to the same address, what's the
> problem?
I took that to mean 'things may be updating concurrently at different
addresses inside an array
'x' is for experimental. things that have a chance to get into the
standard library but are not finished yet. the major differentiator is
that they're not bound by the Go 1 guarantee that nothing changes
(i.e., they can change).
you should be able to find the compiler in
are you following the steps outlined below?
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher
in particular, for a v2 (or v3) it states that the go.mod file must be updated:
> Update the go.mod file to include a /v3 at the end of the module path in the
> module directive
see the "faking time" section here: https://blog.golang.org/playground
not sure if anything has changed since that article
On Sat, Aug 31, 2019 at 4:22 PM robert engels wrote:
> Yes, the code runs fine locally. Reviewing the playground docs, it sees
> that at one point time.Sleep() was a no-op
I'm sorry to say that this list isn't RE2-specific (although one of
the main Go contributors wrote RE2). you will probably get very good
suggestions on how to convert that to Go's regex, which are RE2-like
and I hope you find your answer.
A good additional step to do for this particular list is
l I found is some very
> general stuff. At least it very suspicious. I don't believe that Google can't
> fund such a non-profit initiative without affecting true artists.
>
> And apparently, very unlikely, that you paid a cent to any independent artist
> over that years.
>
>
&
> Funny thing that today Google has announced "official" store for Go-related
> merch, which in it's essence is a try to take away even an even tiny business
> opportunities for artists who were creating some goods and had a very very
> little outcome on this. Now they will have ZERO.
really?
> Google invested in a tool for themselves, which helped a lot in getting some
> zillions of bucks as return. Corps open smth to communities not because they
> a "good", but because at some point they smart enough to make others work for
> free.
I see a "Go Haters Handbook" in the works. I
t;
> I am new to Go and cgo therefore did not exactly understand your point.
> Can you explain me in the context of the code that I had posted.It will
> really help me to get hold of the things much better.
>
> Thanks,
> Nitish
>
> On Wed, Jul 10, 2019 at 5:19 PM andrey mir
Hi Andrey,
>
> I understand the issue here but how can I pass a callback function in a
> struct to C code.I need a struct because I want to pass and an extra
> parameter 'userdata' as well that I would require back as part of callback.
>
> Thanks,
> Nitish
>
> On Wed,
i don't think you can use a go function directly in the callback. you
need a correctly-typed C helper to do it. at least that used to be the
case. see examples:
https://github.com/mirtchovski/clamav/blob/master/cfuncs.go
https://github.com/mirtchovski/clamav/blob/master/callback.go
--
You
easons I dislike exceptions. It's just really hard to reason about such
> jumps in logic especially in massively concurrent programs that go allows us
> to write.
>
>
>
> On Friday, July 5, 2019 at 10:30:43 PM UTC, andrey mirtchovski wrote:
>>
>> > So I was quiet on
> So I was quiet on the topic then - I am not now.
i guess you missed the point where I advocated for a new survey, well
advertised, where all the people who are fervent Go programmers but
somehow neglected to fill out the Go surveys for three years running
can cast their voice. "does go error
;> 0 0% 80.00% 1024.23kB 13.34%
>> github.com/aws/aws-sdk-go/aws/signer/v4.(*signingCtx).build
>> 0 0% 80.00% 1024.23kB 13.34%
>> github.com/aws/aws-sdk-go/aws/signer/v4.SignSDKRequest
>> 0 0% 80.00% 1024.23kB 13.34%
>> git
What I have found useful in the past is pprof's ability to diff profiles.
That means that if you capture heap profiles at regular intervals you can
see a much smaller subset of changes and compare allocation patterns.
On Tue, Jul 2, 2019, 10:53 AM 'Yunchi Luo' via golang-nuts <
"Users don't care about what the designer does. They care about what
they do. If every time you drove a car, you had to learn the meaning
of 100 knobs, the whole system wouldn't work. Simplicity comes from
tuning down the tasks required to drive the car into a certain set of
understood paradigms
> I will let Andrey speak for himself.
Since this is turning into a bit of fisticuffs I will quote my private
message to you for clarity, here it is:
--8<-
Your point is a good one. I agree with your stance.
> Which is why nothing should be done, because every proposal is going to
> go back to what is proven to work - Java and C++ are the dominant languages
> in use today, adding their exception based error handling to Go is ‘the way
> to Go” :)
the battle you're fighting has already been lost. if you want java you
know where to find it :)
--
You received this message
> This issue seems to have resonated with a lot of people, which may be an
> important data point when considering the try proposal
Where were all those people when the Go Surveys were being taken the
last few years? Overwhelmingly, the people have voted error handling
as a major issue. The
Hi Ali,
I understand your desire to provide useful information about Go in
blog posts. This is commendable. However let's try to keep this list
for technical issues and keep empty posts containing just a link to a
minimum. More signal, less noise. Is there a particular issue you'd
like to raise?
collection is not an exported type:
https://github.com/couchbase/moss/blob/master/collection.go#L24
the ?m=all parameter should enable you to see those, but it's not
working for me on your link. perhaps because "collection" and
"Collection" are not considered by godoc to be two different things?
"go mod vendor" will populate the vendor directory in your project,
then "go build -mod=vendor" will only use that directory to build.
On Tue, Jun 11, 2019 at 3:12 AM 唐彦昭 wrote:
>
> I need put my project on the server to compile.But my server can't connect to
> internet.
> So I need to put all
"does it look like the go standard library?"
that style is desirable, yet inimitable
--
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
Atan is implemented in assembly. for amd64 it's just a call to atan
(lowercase a): https://golang.org/src/math/atan_amd64.s
for 386 it is not: https://golang.org/src/math/atan_386.s
On Thu, May 30, 2019 at 9:15 AM rhiro wrote:
>
> I'd like to see the implementation for math.Atan, but I see that
On Fri, May 24, 2019 at 12:49 AM Rob Pike wrote:
>
> If that's true - and it might well not be - it's a surprise to me. When
> launching the language we explicitly made sure NOT to trademark it.
>
Go appears to be trademarked, as well as the new design of the Go
logo. Golang doesn't seem to be.
file an issue, please, if you have not done so already. i'd like to follow it.
On Mon, May 13, 2019 at 8:01 PM Jason E. Aten wrote:
>
> Indeed, confirming data: I can re-create the crashing circumstances
> immediately by renaming C:\Go to C:\Go1.12.5.
>
> On Tuesday, May 14, 2019 at 3:53:10 AM
when you terminate a process the virtual memory associated with that
process ceases to exist. any real memory associated with that process
is not addressable anymore. if another process allocates a page that
maps to a page previously held by the first process will get a
zeroed-out page.
you
https://www.ardanlabs.com/blog/2018/12/garbage-collection-in-go-part1-semantics.html
--
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
macOS doesn't support static linking user binaries. in fact I do see
libSystem linked for each go binary on my Mojave system, including the
simplest non-outputting hello world:
$ cat > t.go
package main; func main(){}
$ go build t.go && otool -L t
t: /usr/lib/libSystem.B.dylib (compatibility
md64\unicode\utf16.a
> packagefile unicode=C:\Go\pkg\windows_amd64\unicode.a
> packagefile internal/race=C:\Go\pkg\windows_amd64\internal\race.a
> packagefile
> internal/syscall/windows/sysdll=C:\Go\pkg\windows_amd64\internal\syscall\windows\sysdll.a
> packagefile
> internal/sysc
> PS F:\GoWorckspace\src\hello> go install
> open E:\temp\go-build447177998\b001\exe\a.out.exe: The system cannot find the
> file specified.
is this a school or work computer? if yes then a group policy may have
disabled the execution of exe files. supply the "-work" argument to go
build. it
try setting GOTMPDIR. not sure what this corresponds to on windows,
but it will change where the go tool will create its temp files:
$ go run -x t.go
WORK=/var/folders/sp/06p28g2d0vs7gd2vhf26wl9mgn/T/go-build126372523
[...]
$ GOTMPDIR=/tmp/go go run -x t.go
WORK=/tmp/go/go-build661115935
> But still, it would seem the range index should be unsigned - what would be
> the purpose of it being signed? Similarly, the slice indexing should be
> unsigned as well. Just thinking about it...
not the first time this has come up. here are a couple of references:
> So, the question is: why ‘i’ isn’t treated as unsigned, since it is a range
> index - won't it always be positive?
The author of the PR was most likely working on Go's tip (what will
become 1.13), where the requirement that the right operator in a shift
is an unsigned integer has been lifted.
Please do! We need to resolve this connundrum for the next 5
generations of computer programmers!
On Wed, Apr 24, 2019 at 8:41 PM David Riley wrote:
>
> On Apr 24, 2019, at 5:25 PM, andrey mirtchovski wrote:
> >
> >> I may easily misremember, but that doesn't matc
> I may easily misremember, but that doesn't match my recollection. I
> don't remember what position Rob and Robert took, but as I recall Ken
> was generally opposed to the ternary operator. He had been in part
> responsible for adding it to C, and felt that it had been a mistake.
>
> Ian
I am
Here's the lore associated with the subject: Ken wanted ternary, Rob
and Robert did not. They overruled Ken (remember, early on all three
had to agree for a feature to go in). The end.
The number of frivolous and egregious abuse of ternary that I've seen
in _modern_ C code is too high.jpg
--
> ? (test) {
> //...do something
> }
> {
> //..do something else
> }
I believe the Go team considered this very carefully early on the
language's development and came to the decision to use "if test" for
"? (test)" and "} else {" for "}{" (without the implied newline). They
also threw in "} else
wolfram alpha is a good place to do numbers:
https://www.wolframalpha.com/input/?i=-1+%3C%3C+31
if you're on a mac, the calculator has a "programmer mode" which
allows arbitrary manipulations of bits.
On Sun, Apr 21, 2019 at 9:36 PM Pat Farrell wrote:
>
> I have a logic error in my calculation.
the go runtime (bare, nothing else) is about 1.1MB now. the "fmt"
package brings almost a MB of dependencies including 800 or so
unicode-related functions (names/symbols), reflection, etc. the math
package brings almost nothing: 11 symbols.
-8<
You need the -benchmem flag to get a report of allocations:
$ go test -bench=. -benchmem
goos: darwin
goarch: amd64
BenchmarkTestSleep_2000-4 1 2005447537 ns/op 456 B/op
3 allocs/op
BenchmarkTestSleep_1000-4 1 1001627153 ns/op 64 B/op
1 allocs/op
On Fri, Apr 19, 2019, 4:48 PM Rob Pike wrote:
> I just use 1 so I don't have to look up what it's called these days, but
> I'm seriously old school.
>
Does that pass code review or do people give you the benefit of doubt?
>
--
You received this message because you are subscribed to the
> offset, err := f.Seek(0, io.SeekCurrent)
my code has been written so long ago i didn't even notice os.SEEK_CUR
is deprecated :)
--
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,
offset, err := f.Seek(0, os.SEEK_CUR)
On Thu, Apr 18, 2019 at 8:50 AM wrote:
>
> I want to know file's current read offset after open a file, but I can not
> found related API.
>
>
>
>
>
> f, err := os.Open("/tmp/")
> if err != nil{
> panic(err)
> }
>
> ... // some read
> So do *not* use go get when manually cloning the project then I take it?
That is correct. For most developers it would be one or more
repositories that contain many modules, not all of which would be
go-gettable anyway.
Also note that "go get" in module mode (outside of GOPATH) will
unpackage
It may help to note that in the earliest references to the Read
interface in the history of the language it accepted a *[]byte, hence
'p' may indeed stand for pointer.
https://github.com/golang/go/commit/7c9e2c2b6c2e0aa3090dbd5183809e1b2f53359b#diff-bf734f53a84f388bf39699d291b06b1d
--
You
There used to be a 512GB heap limit which was removed in Go 1.11.
Currently there should be no heap limit. For additional information
see:
https://github.com/golang/go/commit/2b415549b813ba36caafa34fc34d72e47ee8335c
On Tue, Mar 5, 2019 at 2:08 PM wrote:
>
> I've seen various figures from older
in https://play.golang.org/p/5P5vcebYkGj you're shadowing s by
creating a new variable via :=
this is a common go interview question :)
On Sat, Feb 23, 2019 at 9:34 PM wrote:
>
> Hello,
>
> It's likely that I'm misinterpreting the language spec. It's also easy to
> circumvent by assigning the
reposting my private comment from a day ago for those searching for answers:
try "command-shift-p" or ctrl-shift-p depending on your operating
system, to bring the "all commands" pop-up. there you should be able
to find "Go: Install/Update tools". click on the checkboxes. hit
enter.
On Wed, Feb
There was a change to how go mod treats softlinks in repositories
which changed the hash generated for some packages (we found out the
issue via git.apache.org/thrift.git). If the repo contains softlinks
and you generated your go.mod file before Go 1.11.3 (Go 1.11.2 still
exhibited the bug) then
cray was optimized for throughput, after all ;)
--
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...@googlegroups.com.
For more options, visit
nt to change the contents of
> already published archives.
>
> Julie
>
> On Wed, Jan 23, 2019 at 8:00 PM andrey mirtchovski
> wrote:
>>
>> sorry to be a bother, but are you publishing new archives? will you
>> publish new hashes for the archives with the commands exe
sorry to be a bother, but are you publishing new archives? will you
publish new hashes for the archives with the commands executed thusly?
On Wed, Jan 23, 2019 at 5:12 PM Julie Qiu wrote:
>
> Hello gophers,
>
> Due to an issue with the release tooling (https://golang.org/issue/29906),
>
Incidentally, here's Hoare's proposal for records (structs), and
pointers (references) for Algol 60:
https://archive.computerhistory.org/resources/text/algol/algol_bulletin/A21/P36.HTM
as with most things Hoare has produced, it is very well written and
presents a very good justification for the
> It would sure help if Go had sum types. Has there been any discussion
> of adding these?
one of many, but has links to others: https://github.com/golang/go/issues/19412
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this
this is a case of a variable being reused during a range loop.
essentially k[:] is optimized to something resembling (a pointer to
the memory location of the backing array) which is appended as such to
the [][]int variable. the next iteration it is the same variable in
memory, however it's
The 512GB heap limit was removed in go 1.11. Here's the commit that
did it, it has some additional information:
https://github.com/golang/go/commit/2b415549b813ba36caafa34fc34d72e47ee8335c
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
as https://golang.org/pkg/time/#Date says:
The month, day, hour, min, sec, and nsec values may be outside their
usual ranges and will be normalized during the conversion. For
example, October 32 converts to November 1.
On Tue, Oct 23, 2018 at 3:12 PM wrote:
>
> If you check the source code for
> JavaScript needs a standard - there are many implementations and browsers.
> For the moment, there is only one Go, and I like that.
one go, but two reference implementation. any other implementation is
expected to conscribe to the spec.
--
You received this message because you are subscribed
> Unlikely :-)
>
> The following is much less obscure.
>
> func Shuffle(slice inteface{})
>
> & might have more more sense. e.g.
>
> var cards []card
> ...
> rand.Shuffle(cards)
you've now restricted Shuffle to "shuffling" only slices. and it has
to examine interface{}
> May be it ought to be called FYShuffle?
then we'ld have to rename it if we switched the algorithm (which has
happened once for sort.Sort already). that's not what go is about :)
maybe you're advocating for implementing a Shuffle interface, which
brings us round about to where we are right now
> Well, ok. But I would call “Shuffle” a misleading misnomer, because until the
> user defines a shuffler function (which perversely might not, or might fail
> to, shuffle anything), it does not shuffle anything.
how would you implement shuffle in golang so that it's not a
misleading misnomer?
on mac (and I suppose linux too) you can use fontsrv to extract the
plan 9 font files as acme sees them. on my mac I did:
$ fontsrv -m font
$ acme -f font/GoMono/12a/font
here are screenshots of GoRegular and GoMono in 12a:
https://imgur.com/a/7xnGrmx
I will send you privately a tar of
I do not think this has been shared yet, please accept my apologies if
this is a repeat.
https://www.usenix.org/conference/osdi18/presentation/cutler
The paper contributes Biscuit, a kernel written in Go that implements
enough of POSIX (virtual memory, mmap, TCP/IP sockets, a logging file
On 19 Sep 2018, at 12:23, andrey mirtchovski wrote:
> >
> > you're talking about https://github.com/pkg/profile, presumably. while
> > i did find that fairly quickly and it appears to be very useful, it
> > wasn't immediately obvious that it would solve my particul
you're talking about https://github.com/pkg/profile, presumably. while
i did find that fairly quickly and it appears to be very useful, it
wasn't immediately obvious that it would solve my particular issue.
unfortunately we're also averse to importing third-party packages
without additional
> It's a plausible mistake from any old Unix hand, I think.
anecdotally, i ran into this very same issue yesterday when trying to
instrument a 1.10 go program that allocated (but never used) more than
512 gigabytes of memory. i put in the memprofile saving code as a
deferred closure in main and
> most languages offer programs at least some operating system like services
> via a runtime service layer
> -> in C, this was initially "crt0" the thin c runtime
> -> in Go, the service layer is richer, offering thread management and
> goroutine multiplexing, garbage collection, and more.
>
>
Plenty of previous discussions on the subject. Here's an example from 2012:
https://groups.google.com/d/msg/golang-nuts/wcrZ3P1zeAk/KaR68a8rROEJ
I don't think reasoning has changed.
On Mon, Sep 3, 2018 at 10:38 PM Dat Huynh wrote:
>
> Just a question.
>
> Why does Go allow to call a method
> You're right but I think developers of Go can think about that because its
> benefits are obvious.
can you please enumerate those benefits? many gophers are not
convinced they are obvious.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
it seems from your suggested solutions that you're concerned about cpu
usage. does the goroutine communicate with anything? you can limit its
resources by feeding it less data (via a limiter goroutine) or by
editing it itself do less work (via editing the code)? there is
nothing inherently needed
also useful if you're dealing with blobs of C memory:
https://utcc.utoronto.ca/~cks/space/blog/programming/GoCGoCompatibleStructs
On Sat, May 19, 2018 at 3:03 PM, Jan Mercl <0xj...@gmail.com> wrote:
>
> On Sat, May 19, 2018 at 10:42 PM Max
> wrote:
>
> > The
It is unfortunately not reproducible. I got 2 crashes out of 500
million executions. I've updated to tip and have not seen it since.
On Fri, May 4, 2018 at 12:14 PM, Ian Lance Taylor <i...@golang.org> wrote:
> On Thu, May 3, 2018 at 11:39 PM, andrey mirtchovski
> <mirtchov...@g
> math.Pow does not give as precise answers as the C++ std lib.
math pow doesn't just multiply X by itself Y times, it uses a
different algorithm:
https://golang.org/src/math/pow.go#L40
it would perhaps make sense to quantify the error margins that this
algorithm introduces.
not sure what c++
every time float accuracy is mentioned i think of this:
http://0.30004.com/
--
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
> I’d have thought the case would be the same with the AGPL.
https://opensource.google.com/docs/using/agpl-policy/
--
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
In short, your concurrency is too fine-grained. Adding concurrency
primitives requires locking which is expensive, and creating a lot of
goroutines does consume resources, even if we consider it relatively
cheap.
If you slice the problem slightly differently it can be made faster:
one goroutine
If you're looking for general examples of modern Go, perhaps the
JustForFunc series will be of interest:
https://www.youtube.com/channel/UC_BzFbxG2za3bp5NRRRXJSw
On Fri, Apr 13, 2018 at 10:28 AM, JM wrote:
> thanks. I run a software engineering team so I've been less
Due to Go's compatibility promise most example code written since Go
1.0 should still be relevant, will compile, and will run. Libraries
have grown since 1.0 as our understanding of how to write Go code
improves (context.Context is one such innovation), but the examples in
the documentation are
1 - 100 of 204 matches
Mail list logo