Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ir: Prefer using known semantic parents #1049

Conversation

Projects
None yet
5 participants
@fitzgen
Copy link
Member

fitzgen commented Sep 29, 2017

When choosing a parent ID for a type that we are parsing, prefer known semantic parents over the provided parent ID. It seems like we shouldn't even be passing explicit parent IDs around (they're often buggy), and instead should expand the known_semantic_parent infrastructure, but I'll leave that to some future work.

Fixes #1048

r? @emilio

ir: Prefer using known semantic parents
When choosing a parent ID for a type that we are parsing, prefer known semantic
parents over the provided parent ID. It seems like we shouldn't even be passing
explicit parent IDs around (they're often buggy), and instead should expand the
`known_semantic_parent` infrastructure, but I'll leave that to some future work.

Fixes #1048
@highfive

This comment has been minimized.

Copy link
Collaborator

highfive commented Sep 29, 2017

warning Warning warning

  • These commits modify unsafe code. Please review it carefully!
@emilio

This comment has been minimized.

Copy link
Collaborator

emilio commented Oct 1, 2017

@bors-servo r+

Thanks!

@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Oct 1, 2017

📌 Commit 64d73c2 has been approved by emilio

@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Oct 1, 2017

⌛️ Testing commit 64d73c2 with merge e9169b3...

bors-servo added a commit that referenced this pull request Oct 1, 2017

Auto merge of #1049 - fitzgen:wrong-parent-id-with-nested-class-decla…
…rations, r=emilio

ir: Prefer using known semantic parents

When choosing a parent ID for a type that we are parsing, prefer known semantic parents over the provided parent ID. It seems like we shouldn't even be passing explicit parent IDs around (they're often buggy), and instead should expand the `known_semantic_parent` infrastructure, but I'll leave that to some future work.

Fixes #1048

r? @emilio
@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Oct 1, 2017

💔 Test failed - status-travis

@ctaggart

This comment has been minimized.

Copy link

ctaggart commented Oct 2, 2017

Is this a valid test failure or does CI just need to run again?

@fitzgen

This comment has been minimized.

Copy link
Member Author

fitzgen commented Oct 2, 2017

Is this a valid test failure or does CI just need to run again?

Restarted. Unsure why it was cancelled...

@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Oct 2, 2017

☀️ Test successful - status-travis
Approved by: emilio
Pushing e9169b3 to master...

@bors-servo bors-servo merged commit 64d73c2 into rust-lang:master Oct 2, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details

@bors-servo bors-servo referenced this pull request Oct 2, 2017

Merged

Strongly type ids #1050

4 of 4 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.