Uh oh!
There was an error while loading. Please reload this page.
resolve: Always resolve visibilities on impl items - #67236
Merged
Conversation
This was referenced Dec 11, 2019
petrochenkov
commented
Dec 11, 2019
ContributorAuthor
I'm going to stable-nominate this as well in case there's going to be a point release for other reasons, because this PR fixes a relatively recent stable-to-stable regression that allows erroneous code to be silently accepted. |
matthewjasper
commented
Dec 11, 2019
Contributor
@bors r+ |
bors
commented
Dec 11, 2019
Collaborator
📌 Commit 914c9aa has been approved by |
JohnTitor added a commit
to JohnTitor/rust
that referenced
this pull request
Dec 12, 2019
resolve: Always resolve visibilities on impl items Fixesrust-lang#64705. Similarly to rust-lang#67106 this was an issue with visitor discipline. Impl items were visited as a part of visiting `ast::ItemKind::Impl`, but they should be visit-able in isolation from their parents as well, because that's how they are visited when they are expanded from macros. I've checked that all the remaining `resolve_visibility` calls are used correctly. r? @matthewjasper
bors added a commit
that referenced
this pull request
Dec 12, 2019
Rollup of 8 pull requests Successful merges: - #62514 (Clarify `Box<T>` representation and its use in FFI) - #66983 (Fix `unused_parens` triggers on macro by example code) - #67215 (Fix `-Z print-type-sizes`'s handling of zero-sized fields.) - #67230 (Remove irelevant comment on `register_dtor`) - #67236 (resolve: Always resolve visibilities on impl items) - #67237 (Some small readability improvements) - #67238 (Small std::borrow::Cow improvements) - #67239 (Make TinyList::remove iterate instead of recurse) Failed merges: r? @ghost
pnkfelix
commented
Dec 12, 2019
Contributor
discussed at T-compiler meeting. accepted for beta backport. |
Merged
bors added a commit
that referenced
this pull request
Dec 14, 2019
[beta] Beta backports Backporting the following pull requests: * resolve: Always resolve visibilities on impl items #67236 * resolve: Resolve visibilities on fields with non-builtin attributes #67106 * E0023: handle expected != tuple pattern type #67044 * Fix `unused_parens` triggers on macro by example code #66983 * Fix some issues with attributes on unnamed fields #66669 * Ensure that we get a hard error on generic ZST constants if their bodies #67134 (via #67297) Some of these conflicted on merge, I resolved where possible, sometimes by cherry-picking a commit or two more from the relevant PRs. Since those changes are necessary though for backport to proceed (otherwise not even std/core compile), seems fine -- they're fairly minor cleanups anyway.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes#64705.
Similarly to #67106 this was an issue with visitor discipline.
Impl items were visited as a part of visiting
ast::ItemKind::Impl, but they should be visit-able in isolation from their parents as well, because that's how they are visited when they are expanded from macros.I've checked that all the remaining
resolve_visibilitycalls are used correctly.r? @matthewjasper