How to speed up the Rust compiler in 2022 • Hacker News Board

Re: How to speed up the Rust compiler in 2022

#21

Post by saghm » Sat, Feb 26, 2022, 5:02 AM UTC

mamcx wrote: post #19

leshow wrote: post #18

Earlier quoted context omitted.

Simpler in what way? There are efforts to make writing Rust simpler, to make lifetime elision better or have the borrowck accept more valid programs. I don't think it's reasonable to expect Rust to explore removing language features though.

Example: - Exist 2 ways to do macros. - Exist different ways to annotate traits (impl and the long way) - Alias work, but not everywhere - The module system is too complicated - You have pub and pub(crate). The second must have been the default for types on a crate because the way how things are because modules - The trait system is full of "but" that make it not as simple to use in practice (ej: Is too common traits…

> - The trait system is full of "but" that make it not as simple to use in practice (ej: Is too common traits require extra work because this or that rule in THIS case must be appeased, and also, is where is more obvious things are in disconnect with the rest of the lang)

Can you give a concrete example of what you mean here? I don't doubt that you have a legitimate criticism, but it's phrased in a way that I genuinely am not able to understand

Re: How to speed up the Rust compiler in 2022

#22

Post by estebank » Mon, Feb 28, 2022, 6:16 PM UTC

saghm wrote: post #21

mamcx wrote: post #19

Earlier quoted context omitted.

Example: - Exist 2 ways to do macros. - Exist different ways to annotate traits (impl and the long way) - Alias work, but not everywhere - The module system is too complicated - You have pub and pub(crate). The second must have been the default for types on a crate because the way how things are because modules - The trait system is full of "but" that make it not as simple to use in practice (ej: Is too common traits…

> - The trait system is full of "but" that make it not as simple to use in practice (ej: Is too common traits require extra work because this or that rule in THIS case must be appeased, and also, is where is more obvious things are in disconnect with the rest of the lang) Can you give a concrete example of what you mean here? I don't doubt that you have a legitimate criticism, but it's phrased in a way that I genuine…

This is a great example of where the way people use the word "simple" comes along with lots of caveats and mean different things to each one of us. Increasing simplicity in the user experience (by removing seemingly arbitrary restrictions to the type system) mean increasing the complexity of the implementation. We've already seen that with match ergonomics, the borrow checker and async: "adding complexity" results in "a simpler to use" language.

Re: How to speed up the Rust compiler in 2022

#23

Post by leshow » Sat, Mar 05, 2022, 10:19 PM UTC

mamcx wrote: post #19

leshow wrote: post #18

Earlier quoted context omitted.

Simpler in what way? There are efforts to make writing Rust simpler, to make lifetime elision better or have the borrowck accept more valid programs. I don't think it's reasonable to expect Rust to explore removing language features though.

Example: - Exist 2 ways to do macros. - Exist different ways to annotate traits (impl and the long way) - Alias work, but not everywhere - The module system is too complicated - You have pub and pub(crate). The second must have been the default for types on a crate because the way how things are because modules - The trait system is full of "but" that make it not as simple to use in practice (ej: Is too common traits…

You have just listed a bunch of things as if they are evidence of something, but they are not.