Why didn’t they update to the go’s latest version?
-
-
-
They did at the time that they did this work; this was done last year. Elsewhere they said they tried 1.8 -> 1.10
- 1 more reply
New conversation -
-
-
-
Gotta love compile-time garbage collection (which is basically what Rust does)! :D
End of conversation
New conversation -
-
-
Do the spikes reproduce with the latest Go version? (1.14) If so did you consider filing a bug? This is not normal behavior and it is probably a bug the runtime folks would like to address :)
-
But of unfair comparing Go 1.9 to rust, there have been lots of improvements around GC in more recent version. Still generics has a point
End of conversation
New conversation -
-
-
Pt. 2 Why Discord is a mess anyway
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
killer post. curious if you've gotten to the scale where compile times are a concern yet, and if so how you're handling it (with this recent post in mind: https://pingcap.com/blog/rust-compilation-model-calamity/ …)
-
Not really. We split our code into individual crates. So it only needs to compile the current crate that is being worked on. We don't have to use --release very often, only when doing an actual release. I use "cargo watch" while writing code and that does a quick "cargo check".
End of conversation
New conversation -
-
-
Great read.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.