bors d78329b92e Auto merge of #119088 - George-lewis:glewis/suggest-upgrading-compiler, r=Nilstrieb ... Suggest Upgrading Compiler for Gated Features This PR addresses #117318 I have a few questions: 1. Do we want to specify the current version and release date of the compiler? I have added this in via environment variables, which I found in the code for the rustc cli where it handles the `--version` flag a. How can I handle the changing message in the tests? 3. Do we want to only show this message when the compiler is old? a. How can we determine when the compiler is old? I'll wait until we figure out the message to bless the tests		2024-01-13 20:06:03 +00:00
..
ast_validation.rs	Allow ~const on assoc ty bounds again	2024-01-12 17:22:18 +01:00
errors.rs	Allow ~const on assoc ty bounds again	2024-01-12 17:22:18 +01:00
feature_gate.rs	Add check for ui_testing via promoting parameters from ParseSess to Session	2024-01-13 12:11:13 -05:00
lib.rs	Use rustc_fluent_macro::fluent_messages! directly.	2023-11-26 08:38:40 +11:00
node_count.rs	Remove unused span argument from walk_fn.	2022-09-12 13:24:27 +10:00
show_span.rs	Rename {create,emit}_warning as {create,emit}_warn.	2024-01-10 07:33:06 +11:00