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

"on-demandify" privacy and access levels #40771

Merged
merged 3 commits into from
Mar 26, 2017

Conversation

nikomatsakis
Copy link
Contributor

@eddyb
Copy link
Member

eddyb commented Mar 23, 2017

@bors r+

@bors
Copy link
Contributor

bors commented Mar 23, 2017

📌 Commit bc319b6 has been approved by eddyb

@eddyb
Copy link
Member

eddyb commented Mar 23, 2017

@bors r- Travis failed

@nikomatsakis nikomatsakis force-pushed the issue-40746-privacy-access-levels branch from bc319b6 to 7734c9d Compare March 23, 2017 20:47
I realized that, even in the current system, such reads can't really do
any harm. Because they are not part of a task, they will occur no matter
what (only tasks can be skipped). If you leak the data you read into a
task, that is bad, but that is equally bad if you are in a task.

*Writes* to tracked state, on the other hand, should never occur except
from within a task (and the task then records what things you read to
compute it).

Once we complete the shift to on-demand, these properties will hold by
construction (because the on-demand struct enforces stateless tasks
where leaks are impossible -- except by having shared mutable state in
the tcx).
@nikomatsakis nikomatsakis force-pushed the issue-40746-privacy-access-levels branch from 7734c9d to a9f6bab Compare March 23, 2017 23:11
@nikomatsakis
Copy link
Contributor Author

@bors r=eddyb

@bors
Copy link
Contributor

bors commented Mar 23, 2017

📌 Commit a9f6bab has been approved by eddyb

bors added a commit that referenced this pull request Mar 25, 2017
Rollup of 11 pull requests

- Successful merges: #40347, #40501, #40516, #40524, #40540, #40642, #40683, #40764, #40778, #40807, #40809
- Failed merges: #40771
bors added a commit that referenced this pull request Mar 25, 2017
Rollup of 11 pull requests

- Successful merges: #40347, #40501, #40516, #40524, #40540, #40642, #40683, #40764, #40778, #40807, #40809
- Failed merges: #40771
@bors
Copy link
Contributor

bors commented Mar 25, 2017

⌛ Testing commit a9f6bab with merge ab05f3a...

@arielb1
Copy link
Contributor

arielb1 commented Mar 25, 2017

@bors retry

@bors
Copy link
Contributor

bors commented Mar 25, 2017

⌛ Testing commit a9f6bab with merge 2625af4...

@bors
Copy link
Contributor

bors commented Mar 25, 2017

💔 Test failed - status-travis

@arielb1
Copy link
Contributor

arielb1 commented Mar 25, 2017

frewsxcv added a commit to frewsxcv/rust that referenced this pull request Mar 25, 2017
…cess-levels, r=eddyb

"on-demandify" privacy and access levels

r? @eddyb
cc @cramertj rust-lang#40746
frewsxcv added a commit to frewsxcv/rust that referenced this pull request Mar 25, 2017
…cess-levels, r=eddyb

"on-demandify" privacy and access levels

r? @eddyb
cc @cramertj rust-lang#40746
@arielb1
Copy link
Contributor

arielb1 commented Mar 25, 2017

bors added a commit that referenced this pull request Mar 26, 2017
Rollup of 7 pull requests

- Successful merges: #40642, #40734, #40740, #40771, #40807, #40820, #40821
- Failed merges:
@bors bors merged commit a9f6bab into rust-lang:master Mar 26, 2017
@nikomatsakis nikomatsakis deleted the issue-40746-privacy-access-levels branch April 14, 2017 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants