Skip to content

Use const-checking to forbid use of unstable features in const-stable functions #76807

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

Merged
merged 6 commits into from
Sep 22, 2020

Conversation

ecstatic-morse
Copy link
Contributor

First step towards #76618.

Currently this code isn't ever hit because qualify_min_const_fn runs first and catches pretty much everything. One exception is const_precise_live_drops, which does not use the newly added code since it runs as part of a separate pass.

Also contains some unrelated refactoring, which is split into separate commits.

r? @oli-obk

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 16, 2020
@ecstatic-morse ecstatic-morse force-pushed the const-checking-staged-api branch from 589e285 to abc7167 Compare September 16, 2020 21:19
@oli-obk
Copy link
Contributor

oli-obk commented Sep 17, 2020

This is a good safety net for the actual changes!

@bors r+

@bors
Copy link
Collaborator

bors commented Sep 17, 2020

📌 Commit abc7167 has been approved by oli-obk

@bors bors 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 Sep 17, 2020
@bors bors merged commit 60b9901 into rust-lang:master Sep 22, 2020
@rustbot rustbot added this to the 1.48.0 milestone Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants