That last question I can answer: https://golang.org/pkg/hash/#Hash
Implementing that interface requires this method.
On Sun, Feb 9, 2020 at 7:52 PM Juliusz Chroboczek wrote:
> It would be helpful if the introduction to the maphash package immediately
> stated that it produces 64-bit values, and
It would be helpful if the introduction to the maphash package immediately
stated that it produces 64-bit values, and perhaps restate the fact that
the value can be safely reduced using bit masking (already there at the
Sum64 method).
I'm not sure what is the purpose of the BlockSize method -- why
The first time I ran go-1.14rc1 on a stock Debian system, I got:
runtime: mlock of signal stack failed: 12
runtime: increase the mlock limit (ulimit -l) or
runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+
fatal error: mlock failed
ulimit -l is at 64, which is also the hard
If you use any dynamic memory strict latency is very very difficult in any
language/platform. I’m not really sure how a platform like Discord has strict
latency requirements - it’s not as if the ‘read badge’ not updating is going to
crash the plane.
As an example a lot of auto systems use Java
On Feb 7, 2020, at 7:24 AM, Everton Marques wrote:
>
> I think Go is way better than Rust, but it is amusing to see why people pick
> one over another.
I think they have very different use cases. Rust is fundamentally a functional
language, which suits it quite well for things functional lang
They have very strict latency requirements. So they can't use a language
with a GC. That's fine, no language is totally universal. You have to pick
the right tool for the job.
Aside from that it would be nice if that 2-minutes GC trigger, that is
mentioned in the text, could be removed or less
