diff options
| author | sl <sl@deckard> | 2023-02-11 04:29:13 +0000 |
|---|---|---|
| committer | sl <sl@deckard> | 2023-02-11 04:29:13 +0000 |
| commit | 7f071685e9b7d9e32c1a9675f7fca0407d18e6e1 (patch) | |
| tree | f3af86654432ced2c8b7f66b5554ada4bf493487 /lib | |
| parent | 28e362d368805ad91e0662fcc9577cb74ef13d4e (diff) | |
/lib/rsc: I am not suggesting that instrumentation be added by the Go compiler to all Go programs in the world: that's clearly inappropriate.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/rsc | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -248,3 +248,4 @@ Ever since I wrote “go get,” we on the core Go team hoped the community woul This past winter, as a side project, I spent some time getting up to speed on suffix array construction algorithms and rewrote index/suffixarray's New implementation (that is, the index builder) to run 3-10X faster in half the memory of the old one. So it sounds like everyone is in favor of the entire generics proposal and all the semantics, and all we have left to hammer out is the bracket characters? Do I have that right? Or perhaps Go will earn a reputation for doing telemetry well and people will say things like "Go is the only software with telemetry you don't need to worry about." I think it's too early to say which would happen. +I am not suggesting that instrumentation be added by the Go compiler to all Go programs in the world: that's clearly inappropriate. |