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
error: Cannot derive `Arbitrary` for `Wrapper` union
--> union.rs:5:10
|
5 | #[derive(kani::Arbitrary)]
| ^^^^^^^^^^^^^^^
|
note: `#[derive(Arbitrary)]` cannot be used for unions such as `Wrapper`
--> union.rs:6:7
|
6 | union Wrapper {
| ^^^^^^^
= note: this error originates in the derive macro `kani::Arbitrary` (in Nightly builds, run with -Z macro-backtrace for more info)
With proc-macro-error2, the error is:
error: Cannot derive `Arbitrary` for `Wrapper` union
= note: `#[derive(Arbitrary)]` cannot be used for unions such as `Wrapper`
--> union.rs:5:10
|
5 | #[derive(kani::Arbitrary)]
| ^^^^^^^^^^^^^^^
|
= note: this error originates in the derive macro `kani::Arbitrary` (in Nightly builds, run with -Z macro-backtrace for more info)
The two notable differences are:
The annotated item (union Wrapper) is no longer included in the error
The first note does not appear after the span.
We should investigate if it's possible to restore the previous behavior.
The text was updated successfully, but these errors were encountered:
As suggested in
GnomedDev/proc-macro-error-2#1 (comment),
turning on the `nightly` feature for `proc-macro-error2` to restore the
previous error message for `derive(Arbitrary)`.
Resolves#3495
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.
The replacement of the unmaintained
proc-macro-error
crate with theproc-macro-error2
crate in #3493 resulted in a diff in the error message Kani emits for https://github.com/model-checking/kani/tree/main/tests/ui/derive-arbitrary/union.With
proc-macro-error
, the error was:With
proc-macro-error2
, the error is:The two notable differences are:
union Wrapper
) is no longer included in the errornote
does not appear after the span.We should investigate if it's possible to restore the previous behavior.
The text was updated successfully, but these errors were encountered: