Skip to content

Make GATs object safe under generic_associated_types_extended feature - #94911

Merged
bors merged 1 commit into
rust-lang:masterfrom
jackh726:gats_extended_2
Apr 2, 2022
Merged

Make GATs object safe under generic_associated_types_extended feature#94911
bors merged 1 commit into
rust-lang:masterfrom
jackh726:gats_extended_2

Conversation

@jackh726

Copy link
Copy Markdown
Member

Based on #94869

Let's say we have

traitStreamingIterator{typeItem<'a>whereSelf:'a;}

And dyn for<'a> StreamingIterator<Item<'a> = &'a i32>.

If we ask (dyn for<'a> StreamingIterator<Item<'a> = &'a i32>): StreamingIterator, then we have to prove that for<'x> (&'x i32): Sized. So, we generate new bound vars to subst for the GAT generics.

Importantly, this doesn't fully verify that these are usable and sound.

r? @nikomatsakis

@rustbotrustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Mar 13, 2022
@rust-highfiverust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 13, 2022
@rust-log-analyzer

This comment has been minimized.

@bors

bors commented Mar 25, 2022

Copy link
Copy Markdown
Collaborator

☔ The latest upstream changes (presumably #95291) made this pull request unmergeable. Please resolve the merge conflicts.

@rust-log-analyzer

This comment has been minimized.

@compiler-errorscompiler-errors left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these changes look good -- the logic you're using to create new bound vars for the GATs is inspired from #87900, right?

r=me once the parent PR lands (and you rebase that first commit out)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was going to say that this should also deny GATs with type parameters, but it seems we already disallow those elsewhere: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1af97ded49aa74d43f72f0c3b70658e9

@bors

bors commented Mar 31, 2022

Copy link
Copy Markdown
Collaborator

☔ The latest upstream changes (presumably #95501) made this pull request unmergeable. Please resolve the merge conflicts.

@jackh726

Copy link
Copy Markdown
MemberAuthor

@bors r=compiler-errors

@bors

bors commented Apr 1, 2022

Copy link
Copy Markdown
Collaborator

📌 Commit d3fe28b has been approved by compiler-errors

@borsbors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 1, 2022
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Apr 1, 2022
…r-errors
Make GATs object safe under generic_associated_types_extended feature
Based on rust-lang#94869
Let's say we have
```rust
trait StreamingIterator {
type Item<'a> where Self: 'a;
}
```
And `dyn for<'a> StreamingIterator<Item<'a> = &'a i32>`.
If we ask `(dyn for<'a> StreamingIterator<Item<'a> = &'a i32>): StreamingIterator`, then we have to prove that `for<'x> (&'x i32): Sized`. So, we generate *new* bound vars to subst for the GAT generics.
Importantly, this doesn't fully verify that these are usable and sound.
r? `@nikomatsakis`
@Dylan-DPC

Copy link
Copy Markdown
Member

failed in rollup

@bors r-

@borsbors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Apr 2, 2022
@compiler-errors

Copy link
Copy Markdown
Contributor

NLL strikes again...

@jackh726

Copy link
Copy Markdown
MemberAuthor

@bors r=compiler-errors

@bors

bors commented Apr 2, 2022

Copy link
Copy Markdown
Collaborator

📌 Commit 52b00db has been approved by compiler-errors

@borsbors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Apr 2, 2022
@bors

bors commented Apr 2, 2022

Copy link
Copy Markdown
Collaborator

⌛ Testing commit 52b00db with merge 8f96ef4...

@bors

bors commented Apr 2, 2022

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: compiler-errors
Pushing 8f96ef4 to master...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Apr 2, 2022
@bors
bors merged commit 8f96ef4 into rust-lang:masterApr 2, 2022
@rustbotrustbot added this to the 1.61.0 milestone Apr 2, 2022
@jackh726
jackh726 deleted the gats_extended_2 branch April 2, 2022 21:25
@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (8f96ef4): comparison url.

Summary:

  • Primary benchmarks: no relevant changes found
  • Secondary benchmarks: no relevant changes found. 1 results were found to be statistically significant but too small to be relevant.
Regressions 😿
(primary)
Regressions 😿
(secondary)
Improvements 🎉
(primary)
Improvements 🎉
(secondary)
All 😿 🎉
(primary)
count101000
mean2N/A0.2%N/AN/ANaN%
maxN/A0.2%N/AN/A0.0%

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression

Footnotes

  1. number of relevant changes

  2. the arithmetic mean of the percent change

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

F-generic_associated_types_extended`#![feature(generic_associated_types_extended)]`merged-by-borsThis PR was explicitly merged by bors.S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants

@jackh726@rust-log-analyzer@bors@Dylan-DPC@compiler-errors@rust-timer@nikomatsakis@rust-highfive@fmease@rustbot