3 ms·
init-time load has become a pet project of mine lately: https://github.com/golang/go/issues/26775 https://github.com/golang/go/issues/26775 A new person on th
by bradfitz 8y ago
init-time load has become a pet project of mine lately:
https://github.com/golang/go/issues/26775 https://github.com/golang/go/issues/26775
A new person on the compiler might be working on that too as a warm-up task.
- kodablah 8y agoNice. Looking at what's exposed in the unicode package (did a tad bit of research [0]), there may be limited opportunities to reduce that since the structs are exposed. Maybe fewer goroutine suspend points between cpu-only tasks inside init, I dunno, not very familiar. Maybe a bunch of structs initialized with only const exprs in their fields could be eval'd at compile time and become a data section in the binary (until mutated maybe or just copied from the data section since there're no public immutable vars). 0 - https://github.com/golang/go/issues/26622 https://github.com/golang/go/issues/26622