cargo currently rebuilds all dependants of a crate instead of just relinking.
when only changing the implementation of a lint, this is unnecessary.
using dylib or cdylib should make it possible to just relink when adding/modifying lints, although it may require slight modifications of the api. if i understand correctly, register_plugins is the only function that really needs to be public, with all the lint structs being basically an implementation detail. this is a unique situation and should allow optimizing the build process.
Description
cargo currently rebuilds all dependants of a crate instead of just relinking.
when only changing the implementation of a lint, this is unnecessary.
using dylib or cdylib should make it possible to just relink when adding/modifying lints, although it may require slight modifications of the api. if i understand correctly, register_plugins is the only function that really needs to be public, with all the lint structs being basically an implementation detail. this is a unique situation and should allow optimizing the build process.
Version
No response
Additional Labels
No response