Could @rustlang support a compacting allocator (not talking about GC)? To reduce page usage after highwater memory events?
-
-
Replying to @nsIAnswers @rustlang
Depends on the solution for GC. The infrastructure needed is basically the same.
1 reply 0 retweets 1 like -
Replying to @pcwalton
I figured GC would depend on explicit code-level annotations. I was hoping for something more automatic (per crate compile flag).
1 reply 0 retweets 0 likes -
Replying to @nsIAnswers
It’s hard because we don’t want to *prevent* people from being able to stash pointers in weird places in unsafe code.
1 reply 0 retweets 0 likes
Replying to @pcwalton @nsIAnswers
Important for OS kernels and syscalls and platform APIs and things like that. But we also want moving GC. Tough balancing act :)
1:01 PM - 7 Nov 2016
0 replies
0 retweets
0 likes
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.