| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-04-03 | Use `cfg(false)` in UI tests | clubby789 | -8/+8 | |
| 2024-02-16 | [AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives | 许杰友 Jieyou Xu (Joe) | -1/+1 | |
| 2023-06-10 | expand: Change how `#![cfg(FALSE)]` behaves on crate root | Vadim Petrochenkov | -4/+15 | |
| Previously it removed all other attributes from the crate root. Now it removes only attributes below itself. So it becomes possible to configure some global crate properties even for fully unconfigured crates. | ||||
| 2023-06-01 | Remember names of `cfg`-ed out items to mention them in diagnostics | Nilstrieb | -0/+22 | |
| `#[cfg]`s are frequently used to gate crate content behind cargo features. This can lead to very confusing errors when features are missing. For example, `serde` doesn't have the `derive` feature by default. Therefore, `serde::Serialize` fails to resolve with a generic error, even though the macro is present in the docs. This commit adds a list of all stripped item names to metadata. This is filled during macro expansion and then, through a fed query, persisted in metadata. The downstream resolver can then access the metadata to look at possible candidates for mentioning in the errors. This slightly increases metadata (800k->809k for the feature-heavy windows crate), but not enough to really matter. | ||||
| 2023-03-23 | Add some tests for the current `#![cfg(FALSE)]` crate behavior | Vadim Petrochenkov | -0/+6 | |
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+7 | |
