4 ms·
Is there a work-in-progress changelog of what we can expect to see in 1.7? I couldn't find one.
by kevinmgranger 10y ago
Is there a work-in-progress changelog of what we can expect to see in 1.7? I couldn't find one.
- 4ad 10y agoVery incomplete: https://tip.golang.org/doc/go1.7.txt https://tip.golang.org/doc/go1.7.txt
- dguaraglia 10y agoThis looks sweet: runtime: support symbolic backtrace of C code in a cgo crash (CL 17761)
- weitzj 10y agoNow what does that mean? What does Fortran have to do with Go? | add support for Fortran (CL 19670, CL 4114)
- 4ad 10y agoYou can now call Fortran code through cgo, from Go.
- 0xmohit 10y agoThere has been significant work on performance and toolchain improvement. See http://dave.cheney.net/2016/04/02/go-1-7-toolchain-improvements http://dave.cheney.net/2016/04/02/go-1-7-toolchain-improveme... for information.
- mattetti 10y agothe main changes are related to the SSA compiler backend and smaller binary files. 1.7 should also better support binary only packages (so vendors can sell compiled packages without providing sources, it kinda works right now but was hacky/buggy).