Arbitrary@reddthat.com to Rust@programming.dev · 1 year agoRust Foundation Security Initiative Reportfoundation.rust-lang.orgexternal-linkmessage-square15fedilinkarrow-up131arrow-down10
arrow-up131arrow-down1external-linkRust Foundation Security Initiative Reportfoundation.rust-lang.orgArbitrary@reddthat.com to Rust@programming.dev · 1 year agomessage-square15fedilink
minus-squareRunAwayFroglinkfedilinkEnglisharrow-up1·1 year agoHello kornel. Assuming you have the data, do you mind sharing how many crates in their latest version use compiler plugins?
minus-squarekornel@lemmyrs.orglinkfedilinkEnglisharrow-up1·1 year agoAt least 69K, which is over half of all crates — https://lib.rs/quote is used almost exclusively for output of proc macros.
minus-squareRunAwayFroglinkfedilinkEnglisharrow-up1·1 year agoOh, we are calling proc-macro crates “compiler plugins”! I didn’t realize.
minus-squarekornel@lemmyrs.orglinkfedilinkEnglisharrow-up1·edit-21 year agoThey are dlopened by the rustc process. You can totally mess with it: https://nitter.net/m_ou_se/status/1368632701448818691
minus-squareRunAwayFroglinkfedilinkEnglisharrow-up2·1 year agoI’m aware. I just find calling the average proc-macro crate a “compiler plugin” a little bit baffling/confusing. Isn’t the term “compiler plugin” reserved for crates/tools that depend on rustc, like clippy?
Hello kornel.
Assuming you have the data, do you mind sharing how many crates in their latest version use compiler plugins?
At least 69K, which is over half of all crates — https://lib.rs/quote is used almost exclusively for output of proc macros.
Oh, we are calling
proc-macrocrates “compiler plugins”! I didn’t realize.They are
dlopened by the rustc process. You can totally mess with it: https://nitter.net/m_ou_se/status/1368632701448818691I’m aware.
I just find calling the average proc-macro crate a “compiler plugin” a little bit baffling/confusing.
Isn’t the term “compiler plugin” reserved for crates/tools that depend on
rustc, likeclippy?