原始推文链接： https://bit.ly/3nyYMvU 持续更新

1. A register-based calling convention for Go functions. Backwards compatible, and should give 5-10% speed improvements across a range of applications.

issue https://github.com/golang/go/issues/40724

2. First class fuzzing support in the Go toolchain. This work has been happening behind the scenes in the dev.fuzz branch for some months, so I hope it will start landing for 1.17.

3. Lazy module loading, which should especially help when developing large projects with deep module dependency graphs.

4. Allowing replacement modules to alias other active modules. Useful when working with temporary forks.

5. A language change! (*[4]int)(x) to get a slice's underlying array pointer, without the use of unsafe. A small addition, but it opens interesting possibilities.


看了一下，似乎就第一个比较值得期待， 3和4可能能让临时改别人写的模块方便一些。
--
修改:fork FROM 121.69.4.*
FROM 121.69.4.*

那个4怎么来的，slice的容量是个变量，怎么写出来常数啊？

【 在 Friz 的大作中提到: 】
: 最后那个看了半天， 原来是slice convert到 array 指针
--
FROM 101.82.56.*

不明白，4不是有了吗
我现在就在用replace啊
【 在 fork 的大作中提到: 】
: 原始推文链接： https://bit.ly/3nyYMvU 持续更新
: 1. A register-based calling convention for Go functions. Backwards compatible, and should give 5-10% speed improvements across a range of applications.
: issue https://github.com/golang/go/issues/40724
: ...................
--
FROM 114.249.22.*

大体上是需要多少写多少，如果实际array够大就转换成功否则panic，这么个意思

【 在 Friz (南海鳄神) 的大作中提到: 】
: array容量就是常量，否则编译报错，
: 这里只是举个例子吧
: 但我在想，要是slice里容量只有2，这里转换有点危险
: ...................
--
FROM 123.112.164.*