Vitalii Kryvenko

> how we reconstruct the 'ast lifetime What do you mean by this? I don't understand what problem this is trying to solve. Could you point out how getting rid...

Today the static stores a `RefCell

Yep. Anyway, I think this matter requires experimentation rather than discussions

There is an ability to override the crate type via `cargo rustc --crate-type cdylib`. This way the lint crates could just omit the `lib.crate-type` declaration in the `Cargo.toml`. So `cargo-marker`...

Yeah, it may make sense to have `--locked` just like [cargo install](https://doc.rust-lang.org/cargo/commands/cargo-install.html#dealing-with-the-lockfile) does. Although it will probably require that we run multiple `cargo build`s for each crate separately because we...

I'll try to look into this more a bit later. I don't think it's reasonably possible to merge all lock files, because all crates in a workspace need to agree...

The more I think about this the more I think that marker should follow a similar behavior that `cargo install` does. This is because lint crates aren't actually library crates....

I'm thinking that lints will be shared by the library owners. Yes, they will still be project specific, but for open source libraries the owner of the library may maintain...

Yes, lints need to be specified in Cargo.toml of the project. This doesn't need to change. Another factoid, is that when having lints in a shared directory for reuse purposes...

One more problem that I've found with the approach of maintaining a separate lock file is in the following setup. - `Cargo.toml` - `.cargo/` - `config.toml` contains a definition of...