normalize use of backticks in compiler messages for libcore/ptr

https://github.com/rust-lang/rust/issues/60532
This commit is contained in:
Samy Kacimi 2019-07-18 22:32:24 +02:00
parent 311376d30d
commit 886fb218ed
No known key found for this signature in database
GPG Key ID: E2294E922F4C56E5
2 changed files with 3 additions and 3 deletions

View File

@ -26,8 +26,8 @@ use crate::ptr::NonNull;
/// Unlike `*mut T`, `Unique<T>` is covariant over `T`. This should always be correct /// Unlike `*mut T`, `Unique<T>` is covariant over `T`. This should always be correct
/// for any type which upholds Unique's aliasing requirements. /// for any type which upholds Unique's aliasing requirements.
#[unstable(feature = "ptr_internals", issue = "0", #[unstable(feature = "ptr_internals", issue = "0",
reason = "use NonNull instead and consider PhantomData<T> \ reason = "use `NonNull` instead and consider `PhantomData<T>` \
(if you also use #[may_dangle]), Send, and/or Sync")] (if you also use `#[may_dangle]`), `Send`, and/or `Sync`")]
#[doc(hidden)] #[doc(hidden)]
#[repr(transparent)] #[repr(transparent)]
#[rustc_layout_scalar_valid_range_start(1)] #[rustc_layout_scalar_valid_range_start(1)]

View File

@ -1,4 +1,4 @@
error[E0658]: use of unstable library feature 'ptr_internals': use NonNull instead and consider PhantomData<T> (if you also use #[may_dangle]), Send, and/or Sync error[E0658]: use of unstable library feature 'ptr_internals': use `NonNull` instead and consider `PhantomData<T>` (if you also use `#[may_dangle]`), `Send`, and/or `Sync`
--> $DIR/issue-49983-see-issue-0.rs:4:30 --> $DIR/issue-49983-see-issue-0.rs:4:30
| |
LL | #[allow(unused_imports)] use core::ptr::Unique; LL | #[allow(unused_imports)] use core::ptr::Unique;