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
The `try_[pin_]init!` versions of the initializer macros are
superfluous. Instead of forcing the user to always write an error in
`try_[pin_]init!` and not allowing one in `[pin_]init!`, combine them
into `[pin_]init!` that defaults the error to
`core::convert::Infallible`, but also allows to specify a custom one.
Projects using pin-init still can provide their own defaulting
initializers using the `try_` prefix.
Signed-off-by: Benno Lossin <lossin@kernel.org>
Copy file name to clipboardExpand all lines: tests/ui/compile-fail/init/missing_pin_data.stderr
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,4 +10,4 @@ error[E0599]: no associated item named `__pin_data` found for struct `Foo` in th
10
10
= help: items from traits can only be used if the trait is implemented and in scope
11
11
= note: the following trait defines an item `__pin_data`, perhaps you need to implement it:
12
12
candidate #1: `HasPinData`
13
-
= note: this error originates in the macro `$crate::try_pin_init` which comes from the expansion of the macro `pin_init` (in Nightly builds, run with -Z macro-backtrace for more info)
13
+
= note: this error originates in the macro `$crate::pin_init` which comes from the expansion of the macro `pin_init` (in Nightly builds, run with -Z macro-backtrace for more info)
0 commit comments