4 ms·
I think Project Loom would fit. It's a remarkably sane approach: https://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.html https://cr.openjdk.java.net/~rp
by Felz 7y ago
I think Project Loom would fit. It's a remarkably sane approach:
https://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.html https://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.ht...
- ceronman 7y agoAs a Java developer I'm really looking forward for Project Loom. I think it's a great approach that avoids the pitfalls of the two-colored functions approach. However, Project Loom doesn't fit into the "zero cost abstraction" paradigm of rust. Project Loom requires quite a lot of support form the JVM runtime: > The main technical mission in implementing continuations — and indeed, of this entire project — is adding to HotSpot the ability to capture, store and resume callstacks not as part of kernel threads. JNI stack frames will likely not be supported. It also still require manual suspension so JIT compiled tight loops will likely still cause a problem.
- stuhood 7y agoI think that that makes it fairly similar to Rust's approach then... compiler support for suspension, and cooperative scheduling.