You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto merge of #147345 - Kivooeo:tidy-flt-fix, r=Kobzol
Tidy: revert `flt` to `ftl`
As was explained here #147191 (comment), this reverting this change because `flt` is incorrect format
Also maybe there is existed PR for that? I didn't found one
Follow up #147191
cc `@GuillaumeGomez`
Copy file name to clipboardExpand all lines: compiler/rustc_codegen_ssa/messages.ftl
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -97,10 +97,10 @@ codegen_ssa_invalid_literal_value = invalid literal value
97
97
98
98
codegen_ssa_invalid_monomorphization_basic_float_type = invalid monomorphization of `{$name}` intrinsic: expected basic float type, found `{$ty}`
99
99
100
-
codegen_ssa_invalid_monomorphization_basic_integer_type = invalid monomorphization of `{$name}` intrinsic: expected basic integer type, found `{$ty}`
101
-
102
100
codegen_ssa_invalid_monomorphization_basic_integer_or_ptr_type = invalid monomorphization of `{$name}` intrinsic: expected basic integer or pointer type, found `{$ty}`
103
101
102
+
codegen_ssa_invalid_monomorphization_basic_integer_type = invalid monomorphization of `{$name}` intrinsic: expected basic integer type, found `{$ty}`
103
+
104
104
codegen_ssa_invalid_monomorphization_cannot_return = invalid monomorphization of `{$name}` intrinsic: cannot return `{$ret_ty}`, expected `u{$expected_int_bits}` or `[u8; {$expected_bytes}]`
const_eval_mutable_ptr_in_final = encountered mutable pointer in final value of {const_eval_intern_kind}
233
233
234
-
const_eval_partial_pointer_in_final = encountered partial pointer in final value of {const_eval_intern_kind}
235
-
.note = while pointers can be broken apart into individual bytes during const-evaluation, only complete pointers (with all their bytes in the right order) are supported in the final value
236
-
237
234
const_eval_nested_static_in_thread_local = #[thread_local] does not support implicit nested statics, please create explicit static items and refer to them instead
const_eval_panic_non_str = argument to `panic!()` in a const context must have type `&str`
304
301
302
+
const_eval_partial_pointer_in_final = encountered partial pointer in final value of {const_eval_intern_kind}
303
+
.note = while pointers can be broken apart into individual bytes during const-evaluation, only complete pointers (with all their bytes in the right order) are supported in the final value
304
+
305
305
const_eval_partial_pointer_read =
306
306
unable to read parts of a pointer from memory at {$ptr}
Copy file name to clipboardExpand all lines: compiler/rustc_lint/messages.ftl
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -392,6 +392,14 @@ lint_improper_ctypes_union_layout_help = consider adding a `#[repr(C)]` or `#[re
392
392
lint_improper_ctypes_union_layout_reason = this union has unspecified layout
393
393
lint_improper_ctypes_union_non_exhaustive = this union is non-exhaustive
394
394
395
+
lint_int_to_ptr_transmutes = transmuting an integer to a pointer creates a pointer without provenance
396
+
.note = this is dangerous because dereferencing the resulting pointer is undefined behavior
397
+
.note_exposed_provenance = exposed provenance semantics can be used to create a pointer based on some previously exposed provenance
398
+
.help_transmute = for more information about transmute, see <https://doc.rust-lang.org/std/mem/fn.transmute.html#transmutation-between-pointers-and-integers>
399
+
.help_exposed_provenance = for more information about exposed provenance, see <https://doc.rust-lang.org/std/ptr/index.html#exposed-provenance>
400
+
.suggestion_with_exposed_provenance = use `std::ptr::with_exposed_provenance{$suffix}` instead to use a previously exposed provenance
401
+
.suggestion_without_provenance_mut = if you truly mean to create a pointer without provenance, use `std::ptr::without_provenance_mut`
402
+
395
403
lint_invalid_asm_label_binary = avoid using labels containing only the digits `0` and `1` in inline assembly
396
404
.label = use a different label that doesn't start with `0` or `1`
397
405
.help = start numbering with `2` instead
@@ -439,14 +447,6 @@ lint_invalid_reference_casting_note_book = for more information, visit <https://
439
447
440
448
lint_invalid_reference_casting_note_ty_has_interior_mutability = even for types with interior mutability, the only legal way to obtain a mutable pointer from a shared reference is through `UnsafeCell::get`
441
449
442
-
lint_int_to_ptr_transmutes = transmuting an integer to a pointer creates a pointer without provenance
443
-
.note = this is dangerous because dereferencing the resulting pointer is undefined behavior
444
-
.note_exposed_provenance = exposed provenance semantics can be used to create a pointer based on some previously exposed provenance
445
-
.help_transmute = for more information about transmute, see <https://doc.rust-lang.org/std/mem/fn.transmute.html#transmutation-between-pointers-and-integers>
446
-
.help_exposed_provenance = for more information about exposed provenance, see <https://doc.rust-lang.org/std/ptr/index.html#exposed-provenance>
447
-
.suggestion_with_exposed_provenance = use `std::ptr::with_exposed_provenance{$suffix}` instead to use a previously exposed provenance
448
-
.suggestion_without_provenance_mut = if you truly mean to create a pointer without provenance, use `std::ptr::without_provenance_mut`
449
-
450
450
lint_lintpass_by_hand = implementing `LintPass` by hand
451
451
.help = try using `declare_lint_pass!` or `impl_lint_pass!` instead
0 commit comments