3 ms·

Oh, I hadn't heard that you guys are looking at Zig-style "targeted" compilation (for lack of a better phrase). That sounds like it entails quite a bit of infra

Oh, I hadn't heard that you guys are looking at Zig-style "targeted" compilation (for lack of a better phrase). That sounds like it entails quite a bit of infrastructure work. Is there a GitHub issue I can follow to keep an eye on progress? Out of curiosity, 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?

estebank 11mo ago
You can see epage's replies to my copy of this comment for an idea of the open questions: https://hachyderm.io/@ekuber/115605792856416650 https://hachyderm.io/@ekuber/115605792856416650 You can look at what is currently effectively staffed at https://rust-lang.github.io/rust-project-goals/#flexible-faster-rust-compilation 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.
- aw1621107 11mo ago
  > You can see epage's replies to my copy of this comment for an idea of the open questions: https://hachyderm.io/@ekuber/115605792856416650 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).

estebank 11mo ago

You can see epage's replies to my copy of this comment for an idea of the open questions: https://hachyderm.io/@ekuber/115605792856416650 https://hachyderm.io/@ekuber/115605792856416650 You can look at what is currently effectively staffed at https://rust-lang.github.io/rust-project-goals/#flexible-faster-rust-compilation 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.

aw1621107 11mo ago
> You can see epage's replies to my copy of this comment for an idea of the open questions: https://hachyderm.io/@ekuber/115605792856416650 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).