Matthias Krüger a660516334 Rollup merge of #117596 - thomcc:core_macro_diag_items, r=Nilstrieb ... Add diagnostic items for a few of core's builtin macros Specifically, `env`, `option_env`, and `include`. There are a number of reasons why people might want to look at these in lints (For example, to ensure that things behave consistently, detect things that might make builds less reproducible, etc). Concretely, in PL/Rust (well, `plrustc`) we have lints that forbid these (which I'd like to [add to clippy as restriction lints](https://rust-lang.zulipchat.com/#narrow/stream/257328-clippy/topic/Landing.20a.20flotilla.20of.20lints.3F) eventually), and `dylint` also has [lints that look for `env!`/`option_env!`](109a07e9f2/examples/general/env_cargo_path/src/lib.rs) (although perhaps not `include`), which would benefit from this. My experience is that it's pretty annoying to (robustly) check uses of builtin macros without these IME, although that's perhaps just my own fault (e.g. I could be doing it wrong). At `@Nilstrieb's` suggestion, I've added a comment that explains why these are here, even though they are not used in the compiler. This is mostly to discourage removal, although it's not a big deal if it happens (I'm certainly not suggesting the presence of these be in any way stable). --- In theory this is a library PR (in that it's in library/core), but I'm going to roll compiler because the existence of this or not is much more likely something they care about rather than libs. Hopefully nobody objects to this. r? compiler		2023-11-05 12:41:48 +01:00
..
benches	fix	2023-07-23 09:58:31 +00:00
src	Rollup merge of #117596 - thomcc:core_macro_diag_items, r=Nilstrieb	2023-11-05 12:41:48 +01:00
tests	Auto merge of #116218 - tgross35:const-maybe-uninit-zeroed, r=dtolnay	2023-11-05 05:56:21 +00:00
Cargo.toml	Update rand in the stdlib tests, and remove the getrandom feature from it	2023-01-04 14:52:41 -08:00