Skip to content

Visibility tokens on types in extern { ... } blocks are no longer given to procedural macrosΒ #69315

Closed
@alexcrichton

Description

@alexcrichton

I had rustwasm/wasm-bindgen#2009 opened up on a project recently but this looks to be a regression I think. This regressed between nightly-2020-02-19 and nightly-2020-02-20, and bisecting further by commit reveals #69271 as the culprit. I'm not sure which of the PRs in that rollup though are the culprit here.

This can be reproduced by running cargo check from the crates/js-sys folder in the wasm-bindgen repository. Unfortunately this one probably isn't super easy to reproduce, so I'm hoping that someone more knowledgeable can hopefully take a look at this and have a better idea about what's going on.

There's definitely macros going on in #[wasm_bindgen] (the Memory type is synthesized by a macro), which leads me to think that #69211 may be the culprit? (cc @petrochenkov)

Metadata

Metadata

Labels

A-parserArea: The lexing & parsing of Rust source code to an ASTA-visibilityArea: Visibility / privacyT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions