An interesting feedback loop - we sometimes make things explicit in Rust because of niche performance needs, e.g., Rc vs Arc
-
(I should stop doing that, but on the other hand I personally enjoy micro-optimizing stuff far too much)
*Writing library about to perform network IO* We should try to avoid allocating a string here.
-
-
You know as well as i do that I’d *at least* demand a comment assuring me that string will never grow to be above, say, 16MB :P
-
And now I’m trying to combine “micro-optimize” and “paranoia” into a single word with less than 6 syllables
- 2 more replies
New conversation -
-
-
on the other side of this is stuff like https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/EUqoIz2iFU4/kPZ5ZK0K3gEJ … with 25k allocations per keystroke
-
perhaps this would be easier to avoid in a language without implicit cloning and with safe references you can use confidently more often...
- 7 more replies
New conversation -
-
-
Interestingly, now I tend to avoid allocations, not because of their timing cost, but because alloc*nb of connections often ends badly
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.