mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
65f92a52bf
rust/tests/ui/proc-macro/disappearing-resolution.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

27 lines
860 B
Plaintext
Raw Normal View History

resolve: Remove an incorrect assert
2019-10-05 15:28:49 -05:00
error: cannot find attribute `empty_helper` in this scope
--> $DIR/disappearing-resolution.rs:18:3
|
LL | #[empty_helper]
| ^^^^^^^^^^^^
resolve: Say "import" when reporting private imports
2020-01-12 07:20:57 -06:00
error[E0603]: derive macro import `Empty` is private
resolve: Remove an incorrect assert
2019-10-05 15:28:49 -05:00
--> $DIR/disappearing-resolution.rs:11:8
|
LL | use m::Empty;
Normalize wording of privacy access labels
2020-03-22 17:36:54 -05:00
| ^^^^^ private derive macro import
resolve: Point at the private item definitions in privacy errors
2020-01-12 07:04:03 -06:00
|
Serialize all foreign `SourceFile`s into proc-macro crate metadata Normally, we encode a `Span` that references a foreign `SourceFile` by encoding information about the foreign crate. When we decode this `Span`, we lookup the foreign crate in order to decode the `SourceFile`. However, this approach does not work for proc-macro crates. When we load a proc-macro crate, we do not deserialzie any of its dependencies (since a proc-macro crate can only export proc-macros). This means that we cannot serialize a reference to an upstream crate, since the associated metadata will not be available when we try to deserialize it. This commit modifies foreign span handling so that we treat all foreign `SourceFile`s as local `SourceFile`s when serializing a proc-macro. All `SourceFile`s will be stored into the metadata of a proc-macro crate, allowing us to cotinue to deserialize a proc-macro crate without needing to load any of its dependencies. Since the number of foreign `SourceFile`s that we load during a compilation session may be very large, we only serialize a `SourceFile` if we have also serialized a `Span` which requires it.
2020-06-24 12:16:36 -05:00
note: the derive macro import `Empty` is defined here...
resolve: Point at the private item definitions in privacy errors
2020-01-12 07:04:03 -06:00
--> $DIR/disappearing-resolution.rs:9:9
|
LL | use test_macros::Empty;
| ^^^^^^^^^^^^^^^^^^
Serialize all foreign `SourceFile`s into proc-macro crate metadata Normally, we encode a `Span` that references a foreign `SourceFile` by encoding information about the foreign crate. When we decode this `Span`, we lookup the foreign crate in order to decode the `SourceFile`. However, this approach does not work for proc-macro crates. When we load a proc-macro crate, we do not deserialzie any of its dependencies (since a proc-macro crate can only export proc-macros). This means that we cannot serialize a reference to an upstream crate, since the associated metadata will not be available when we try to deserialize it. This commit modifies foreign span handling so that we treat all foreign `SourceFile`s as local `SourceFile`s when serializing a proc-macro. All `SourceFile`s will be stored into the metadata of a proc-macro crate, allowing us to cotinue to deserialize a proc-macro crate without needing to load any of its dependencies. Since the number of foreign `SourceFile`s that we load during a compilation session may be very large, we only serialize a `SourceFile` if we have also serialized a `Span` which requires it.
2020-06-24 12:16:36 -05:00
note: ...and refers to the derive macro `Empty` which is defined here
--> $DIR/auxiliary/test-macros.rs:25:1
|
LL | pub fn empty_derive(_: TokenStream) -> TokenStream {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ consider importing it directly
resolve: Remove an incorrect assert
2019-10-05 15:28:49 -05:00
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0603`.
Reference in New Issue Copy Permalink