rust/tests/ui/interior-mutability/interior-mutability.stderr

error[E0277]: the type `UnsafeCell<i32>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
  --> $DIR/interior-mutability.rs:5:18
   |
LL |     catch_unwind(|| { x.set(23); });
   |     ------------ ^^^^^^^^^^^^^^^^^ `UnsafeCell<i32>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
   |     |
   |     required by a bound introduced by this call
   |
   = help: within `Cell<i32>`, the trait `RefUnwindSafe` is not implemented for `UnsafeCell<i32>`
note: required because it appears within the type `Cell<i32>`
  --> $SRC_DIR/core/src/cell.rs:LL:COL
   = note: required for `&Cell<i32>` to implement `UnwindSafe`
note: required because it's used within this closure
  --> $DIR/interior-mutability.rs:5:18
   |
LL |     catch_unwind(|| { x.set(23); });
   |                  ^^
note: required by a bound in `catch_unwind`
  --> $SRC_DIR/std/src/panic.rs:LL:COL

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			error[E0277]: the type `UnsafeCell<i32>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
Rework point-at-arg 2022-08-16 06:27:22 +00:00			`--> $DIR/interior-mutability.rs:5:18`
Changing error message for interior mutability, adding ui test 2017-06-01 15:46:26 +05:30			`\|`
Add message to `rustc_on_unimplemented` attributes in core 2018-06-09 16:53:36 -07:00			`LL \| catch_unwind(\|\| { x.set(23); });`
Rework point-at-arg 2022-08-16 06:27:22 +00:00			\| ------------ ^^^^^^^^^^^^^^^^^ `UnsafeCell<i32>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
			`\| \|`
			`\| required by a bound introduced by this call`
Remove trailing whitespace from error messages 2021-06-10 13:52:00 +02:00			`\|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			= help: within `Cell<i32>`, the trait `RefUnwindSafe` is not implemented for `UnsafeCell<i32>`
rustc_middle: Fix `opt_item_ident` for non-local def ids 2023-05-03 19:27:29 +03:00			note: required because it appears within the type `Cell<i32>`
			`--> $SRC_DIR/core/src/cell.rs:LL:COL`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 21:31:37 +01:00			= note: required for `&Cell<i32>` to implement `UnwindSafe`
Greatly improve error reporting for futures and generators in `note_obligation_cause_code` Most futures don't go through this code path, because they're caught by `maybe_note_obligation_cause_for_async_await`. But all generators do, and `maybe_note` is imperfect and doesn't catch all futures. Improve the error message for those it misses. At some point, we may want to consider unifying this with the code for `maybe_note_async_await`, so that `async_await` notes all parent constraints, and `note_obligation` can point to yield points. But both functions are quite complicated, and it's not clear to me how to combine them; this seems like a good incremental improvement. 2022-06-19 13:59:36 -05:00			`note: required because it's used within this closure`
			`--> $DIR/interior-mutability.rs:5:18`
			`\|`
			`LL \| catch_unwind(\|\| { x.set(23); });`
Shorten span for closures. 2022-06-27 07:45:35 +02:00			`\| ^^`
Use note to point at bound introducing requirement 2021-07-31 09:26:55 -07:00			note: required by a bound in `catch_unwind`
			`--> $SRC_DIR/std/src/panic.rs:LL:COL`
Changing error message for interior mutability, adding ui test 2017-06-01 15:46:26 +05:30
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 16:09:09 +03:00			`error: aborting due to previous error`
Changing error message for interior mutability, adding ui test 2017-06-01 15:46:26 +05:30
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0277`.