by soroso on 8/24/18, 10:28 PM with 48 comments
by bradfitz on 8/24/18, 11:59 PM
https://golang.org/doc/go1.11#performance-compiler
> The compiler now performs significantly more aggressive bounds-check and branch elimination. Notably, it now recognizes transitive relations, so if i<j and j<len(s), it can use these facts to eliminate the bounds check for s[i]. It also understands simple arithmetic such as s[i-10] and can recognize more inductive cases in loops. Furthermore, the compiler now uses bounds information to more aggressively optimize shift operations.
by bradfitz on 8/25/18, 1:15 AM
https://docs.google.com/presentation/d/1EwuJhEHR5Trr2aXBPQaj...
(See speaker notes for more context)
by dlojudice on 8/24/18, 10:55 PM
considering it includes the runtime, this isn't a large file compared to images / videos you find on the web today
by gaddferreira on 8/24/18, 11:42 PM
I'm very optimistic that the modules system is another step in the right direction, however long it took to get here. Thanks everyone working on Go.
by 0xmohit on 8/24/18, 10:58 PM
Information about modules can be found at:
- https://golang.org/cmd/go/#hdr-Preliminary_module_support
- https://github.com/golang/go/wiki/Modules
- https://research.swtch.com/vgo
The wiki - https://golang.org/wiki/WebAssembly - provides information on how to get started with using Wasm with Go.
by int_19h on 8/25/18, 6:08 AM
I wonder when Go is planning to stop using the kernel ABI on BSDs and macOS directly - in direct contradiction to stability guarantees (or lack thereof) by those platforms - and start using the appropriate APIs, such as libc. Or is it going to be stuff like this or https://github.com/golang/go/issues/16606 forever? Right now, I stay away from Go partly because of this - it feels like a bad idea to use a software stack that is guaranteed to be broken on future OS releases by design. Especially when that stack is advertised specifically for system programming...
by alexandernst on 8/24/18, 10:57 PM
by lsllc on 8/25/18, 12:40 AM
Most exciting thing [which isn't really a thing] is that they've reserved RISC-V GOARCH values!!!!!!!!!!!! Looking forward to RISC-V everywhere!
by Sileni on 8/24/18, 10:55 PM
by mathnode on 8/24/18, 10:44 PM
Thanks everyone at golang.