| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-01-24 | Remove quote_*! macros and associated APIs | Mark Simulacrum | -17/+0 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2015-02-12 | Warn when linking a plugin into a non-plugin crate | Keegan McAllister | -0/+1 | |
| Fixes #22202. | ||||
| 2015-02-09 | Use a crate attribute to load plugins | Keegan McAllister | -0/+26 | |
| #[plugin] #[no_link] extern crate bleh; becomes a crate attribute #![plugin(bleh)] The feature gate is still required. It's almost never correct to link a plugin into the resulting library / executable, because it will bring all of libsyntax and librustc with it. However if you really want this behavior, you can get it with a separate `extern crate` item in addition to the `plugin` attribute. Fixes #21043. Fixes #20769. [breaking-change] | ||||
