Change:
This program: Produces this output: Note the references to ; these symbols have been superseded by associated consts at (). the error message to suggest the new symbols if any of the other old symbols are contained in any error messages. <!-- TRIAGEBOTSTART --<!-- TRIAGEBOTASSIGNSTART --<!-- TRIAGEBOTASSIGNDATASTARTTRIAGEBOTASSIGNDATAEND --<!-- TRIAGEBOTASSIGNEND --<!-- TRIAGEBOTEND --
See also .
I am working on this. claim
: I've gone and grepped through for , , etc. and found no accidental uses there. I then grepped for each of the individual symbols listed in RFC 2700 (, , etc.) and didn't notice anything out of place. I also grepped for (as seen in this issue) and found only a hint message for things like etc which only triggers when an item isn't found at all, which won't trigger for any of the new consts. Probably safe to close this once merges.
You are right. I was thinking of cases like this one but this can likely be closed with the merge of that PR. I was operating with an abundance of caution.
Yeah, that's the aforementioned case that only shows up in the event of an error, so (AFAICT) that path won't be taken for the new constants since they resolve successfully.

Discussion:
cx.struct_span_lint(OVERFLOWING_LITERALS, e.span, |lint| { lint.build(&format!("literal out of range for `{}`", t.name_str())) .note(&format!( <del> "the literal `{}` does not fit into the type `{}` and will be converted to `std::{}::INFINITY`", </del> <ins> "the literal `{}` does not fit into the type `{}` and will be converted to `{}::INFINITY`", </ins> cx.sess() .source_map() .span_to_snippet(lit.span)

LL |     let x = -3.40282357e+38_f32; |              ^^^^^^^^^^^^^^^^^^ | <del> = note: the literal `3.40282357e+38_f32` does not fit into the type `f32` and will be converted to `std::f32::INFINITY` </del> <ins> = note: the literal `3.40282357e+38_f32` does not fit into the type `f32` and will be converted to `f32::INFINITY` </ins> error: literal out of range for `f32` --> $DIR/lint-type-overflow2.rs:10:14

LL |     let x =  3.40282357e+38_f32; |              ^^^^^^^^^^^^^^^^^^ | <del> = note: the literal `3.40282357e+38_f32` does not fit into the type `f32` and will be converted to `std::f32::INFINITY` </del> <ins> = note: the literal `3.40282357e+38_f32` does not fit into the type `f32` and will be converted to `f32::INFINITY` </ins> error: literal out of range for `f64` --> $DIR/lint-type-overflow2.rs:11:14

LL |     let x = -1.7976931348623159e+308_f64; |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | <del> = note: the literal `1.7976931348623159e+308_f64` does not fit into the type `f64` and will be converted to `std::f64::INFINITY` </del> <ins> = note: the literal `1.7976931348623159e+308_f64` does not fit into the type `f64` and will be converted to `f64::INFINITY` </ins> error: literal out of range for `f64` --> $DIR/lint-type-overflow2.rs:12:14

LL |     let x =  1.7976931348623159e+308_f64; |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | <del> = note: the literal `1.7976931348623159e+308_f64` does not fit into the type `f64` and will be converted to `std::f64::INFINITY` </del> <ins> = note: the literal `1.7976931348623159e+308_f64` does not fit into the type `f64` and will be converted to `f64::INFINITY` </ins> error: aborting due to 5 previous errors