Arbitrary@reddthat.com to Rust@programming.dev · 2 年前Rust Foundation Security Initiative Reportfoundation.rust-lang.orgexternal-linkmessage-square12fedilinkarrow-up129arrow-down10
arrow-up129arrow-down1external-linkRust Foundation Security Initiative Reportfoundation.rust-lang.orgArbitrary@reddthat.com to Rust@programming.dev · 2 年前message-square12fedilink
minus-squareRunAwayFrog@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 年前Oh, we are calling proc-macro crates “compiler plugins”! I didn’t realize.
minus-squarekornel@lemmyrs.orglinkfedilinkEnglisharrow-up1·edit-22 年前They are dlopened by the rustc process. You can totally mess with it: https://nitter.net/m_ou_se/status/1368632701448818691
minus-squareRunAwayFrog@sh.itjust.workslinkfedilinkEnglisharrow-up2·2 年前I’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?
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?