Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can see epage's replies to my copy of this comment for an idea of the open questions: https://hachyderm.io/@ekuber/115605792856416650

You can look at what is currently effectively staffed at https://rust-lang.github.io/rust-project-goals/#flexible-fas...

We discussed a lot of these last May in person. Haven't kept track of who's doing what on these fronts.

> have there been any interesting pondered/proposed avenues for speedup that were rejected because they would result in too much breakage, violate a core tenant of Rust (e.g., require a runtime to be usable) or other reason that is "inherent" to Rust?

Yes, but I haven't been part of all of them and can't ellaborate much here. Opening a thread in internals.rust-lang.org with that question might get some good info sooner that I could.



> You can see epage's replies to my copy of this comment for an idea of the open questions: https://hachyderm.io/@ekuber/115605792856416650

Those are some interesting discussions there! Decent number of things I hadn't considered.

> Opening a thread in internals.rust-lang.org with that question might get some good info sooner that I could.

I'll have to see about setting signed up, then (or finding my old credentials; don't remember if I ever had any).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: