May be you can also start looking for @rustlang (iff possible) , just saying. I am pretty sure you are aware of that very much
-
-
-
Just in case you missed a response to a similar comment in another thread:https://twitter.com/jakehughesuk/status/1265330273731911683 …
- 4 more replies
New conversation -
-
-
Such thing are always interesting but.. somewhat skewed to a rather specific model of C++ engine perhaps...pic.twitter.com/IWntTIFTpq
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If you could trace C++ coroutines couldn't you make collection precise kind of like how V8 already does for JS?
-
If you mean C++20's coroutines, the answer is no - in a coroutine state you need to know precisely where your managed pointers are (same as for regular stack). The Standard provides no guarantees on the layout of coroutine states.
End of conversation
New conversation -
-
-
The use of raw pointers for stack-based references makes me uneasy. Wouldn't it make sense to at least provide a wrapper that compiles down to a raw pointer in production builds, so that it'd be possible to swap out the implementation later if it becomes necessary?
-
Also how do valgrind et al respond to things scanning the stack outside of its own stack frame? It feels like that would look like a stack violation to debugging tools. The raw pointer usage also seems like it'd be VERY easy to make mistakes.
- 1 more reply
New conversation -
-
-
Is Rust not an option?
-
Rust is great a lot of the time, but there are cases where its single ownership model is not really suitable. Complex graphs (such as the DOM) are far less painful to work on with a GC.
End of conversation
New conversation -
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.
Learn how Oilpan provides a safe high-performance garbage collection for C++.