Skip to content
This repository has been archived by the owner on Sep 5, 2019. It is now read-only.

Broken on most recent nightly #2

Closed
skade opened this issue Aug 17, 2019 · 7 comments
Closed

Broken on most recent nightly #2

skade opened this issue Aug 17, 2019 · 7 comments

Comments

@skade
Copy link
Contributor

skade commented Aug 17, 2019

I seems like proc_macro_hack broke. Please use rustup override set nightly-2019-08-15 in the meantime.

error: cannot find macro `proc_macro_call_0!` in this scope
   --> src/bin/server.rs:92:9
    |
92  | /         select! {
93  | |             msg = messages.next().fuse() => match msg {
94  | |                 Some(msg) => stream.write_all(msg.as_bytes()).await?,
95  | |                 None => break,
...   |
100 | |             }
101 | |         }
    | |_________^
    |
    = help: have you added the `#[macro_use]` on the module/import?
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
@jamesmunns
Copy link

I think this has been fixed in rust-lang/rust#63667

@jamesmunns
Copy link

jamesmunns commented Aug 18, 2019

Though not yet fixed in the latest nightly:

james@archx1c6g ➜  a-chat git:(master) rustup show
Default host: x86_64-unknown-linux-gnu

# ...

active toolchain
----------------

nightly-x86_64-unknown-linux-gnu (default)
rustc 1.39.0-nightly (2111aed0a 2019-08-17)

james@archx1c6g ➜  a-chat git:(master) cargo clean && cargo build
# ...
   Compiling async-std v0.99.3
   Compiling a-chat v0.1.0 (/tmp/a-chat)
error: cannot find macro `proc_macro_call_1!` in this scope
  --> src/bin/client.rs:31:9
   |
31 | /         select! {
32 | |             line = lines_from_server.next().fuse() => match line {
33 | |                 Some(line) => {
34 | |                     let line = line?;
...  |
46 | |             }
47 | |         }
   | |_________^
   |
   = help: have you added the `#[macro_use]` on the module/import?
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: unused import: `futures::FutureExt`
 --> src/bin/client.rs:6:5
  |
6 | use futures::FutureExt;
  |     ^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error: cannot find macro `proc_macro_call_0!` in this scope
   --> src/bin/server.rs:92:9
    |
92  | /         select! {
93  | |             msg = messages.next().fuse() => match msg {
94  | |                 Some(msg) => stream.write_all(msg.as_bytes()).await?,
95  | |                 None => break,
...   |
100 | |             }
101 | |         }
    | |_________^
    |
    = help: have you added the `#[macro_use]` on the module/import?
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: cannot find macro `proc_macro_call_1!` in this scope
   --> src/bin/server.rs:126:21
    |
126 |           let event = select! {
    |  _____________________^
127 | |             event = events.next().fuse() => match event {
128 | |                 None => break,
129 | |                 Some(event) => event,
...   |
135 | |             },
136 | |         };
    | |_________^
    |
    = help: have you added the `#[macro_use]` on the module/import?
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: unreachable expression
  --> src/bin/client.rs:49:5
   |
49 |     Ok(())
   |     ^^^^^^
   |
   = note: `#[warn(unreachable_code)]` on by default

error: aborting due to previous error

error: Could not compile `a-chat`.
warning: build failed, waiting for other jobs to finish...
warning: unreachable statement
   --> src/bin/server.rs:164:5
    |
164 |     drop(peers);
    |     ^^^^^^^^^^^^
    |
    = note: `#[warn(unreachable_code)]` on by default

warning: unreachable expression
   --> src/bin/server.rs:103:5
    |
103 |     Ok(())
    |     ^^^^^^

warning: unused import: `FutureExt`
  --> src/bin/server.rs:12:5
   |
12 |     FutureExt,
   |     ^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

error: aborting due to 2 previous errors

error: Could not compile `a-chat`.

To learn more, run the command again with --verbose.
james@archx1c6g ➜  a-chat git:(master)

@jamesmunns
Copy link

This has been fixed as of rustc 1.39.0-nightly (4cf767307 2019-08-18).

@morlinbrot
Copy link
Contributor

Doesn't work with that version either:

~/prx/a-chat  add-rust-toolchain-file ✗                                                           10m ⚑  
▶ rustup show
Default host: x86_64-unknown-linux-gnu
...
active toolchain
----------------

nightly-2019-08-18-x86_64-unknown-linux-gnu (overridden by '/home/synul/prx/a-chat/rust-toolchain')
rustc 1.39.0-nightly (2111aed0a 2019-08-17)

▶ cargo build
   Compiling a-chat v0.1.0 (/home/synul/prx/a-chat)
error: cannot find macro `proc_macro_call_1!` in this scope
  --> src/bin/client.rs:31:9
   |
31 | /         select! {
32 | |             line = lines_from_server.next().fuse() => match line {
33 | |                 Some(line) => {
34 | |                     let line = line?;
...  |
46 | |             }
47 | |         }
   | |_________^
   |
   = help: have you added the `#[macro_use]` on the module/import?
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: unused import: `futures::FutureExt`
 --> src/bin/client.rs:6:5
  |
6 | use futures::FutureExt;
  |     ^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error: cannot find macro `proc_macro_call_0!` in this scope
   --> src/bin/server.rs:92:9
    |
92  | /         select! {
93  | |             msg = messages.next().fuse() => match msg {
94  | |                 Some(msg) => stream.write_all(msg.as_bytes()).await?,
95  | |                 None => break,
...   |
100 | |             }
101 | |         }
    | |_________^
    |
    = help: have you added the `#[macro_use]` on the module/import?
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: cannot find macro `proc_macro_call_1!` in this scope
   --> src/bin/server.rs:126:21
    |
126 |           let event = select! {
    |  _____________________^
127 | |             event = events.next().fuse() => match event {
128 | |                 None => break,
129 | |                 Some(event) => event,
...   |
135 | |             },
136 | |         };
    | |_________^
    |
    = help: have you added the `#[macro_use]` on the module/import?
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: unreachable expression
  --> src/bin/client.rs:49:5
   |
49 |     Ok(())
   |     ^^^^^^
   |
   = note: `#[warn(unreachable_code)]` on by default

error: aborting due to previous error

error: Could not compile `a-chat`.
warning: build failed, waiting for other jobs to finish...
warning: unreachable statement
   --> src/bin/server.rs:164:5
    |
164 |     drop(peers);
    |     ^^^^^^^^^^^^
    |
    = note: `#[warn(unreachable_code)]` on by default

warning: unreachable expression
   --> src/bin/server.rs:103:5
    |
103 |     Ok(())
    |     ^^^^^^

warning: unused import: `FutureExt`
  --> src/bin/server.rs:12:5
   |
12 |     FutureExt,
   |     ^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

error: aborting due to 2 previous errors

error: Could not compile `a-chat`.

To learn more, run the command again with --verbose.

@jamesmunns
Copy link

@synul you need the toolchain one day newer, 2019-08-19 (built 2019-08-18). You were using 2019-08-18, built on the 17th.

@morlinbrot
Copy link
Contributor

Ah, indeed, the newest version works. I updated my PR with the newer version, not sure if that is still needed though...

@ghost
Copy link

ghost commented Aug 22, 2019

I think we can close this since it's been fixed.

@ghost ghost closed this as completed Aug 22, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants