-
Notifications
You must be signed in to change notification settings - Fork 14.1k
contracts: clean up feature flag warning duplicated across tests #149736
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
bors
merged 1 commit into
rust-lang:main
from
dawidl022:contracts/chore/cleanup-warning-in-tests
Dec 8, 2025
Merged
contracts: clean up feature flag warning duplicated across tests #149736
bors
merged 1 commit into
rust-lang:main
from
dawidl022:contracts/chore/cleanup-warning-in-tests
Dec 8, 2025
+50
−512
Conversation
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
jieyouxu
requested changes
Dec 7, 2025
Collaborator
|
Reminder, once the PR becomes ready for a review, use |
42741c0 to
ab2aaa9
Compare
Contributor
Author
|
@rustbot ready |
This comment has been minimized.
This comment has been minimized.
There is no need for every contracts test to assert the same warning for using the `contracts` feature flag, as such use `#![expect(incomplete_features)]` in the tests, and add one test to specifically check for the warning.
ab2aaa9 to
0bd9a2f
Compare
Member
|
@bors r=Kivooeo,jieyouxu rollup |
Collaborator
bors
added a commit
that referenced
this pull request
Dec 8, 2025
Rollup of 8 pull requests Successful merges: - #148935 (Fix division syntax in doc comments) - #149207 (Add `ilog10` result range hints) - #149676 (Tidying up tests/ui/issues tests [3/N]) - #149710 (Move ambient gdb discovery from compiletest to bootstrap) - #149714 (Check associated type where-clauses for lifetimes) - #149722 (contracts: fix lowering final declaration without trailing semicolon) - #149736 (contracts: clean up feature flag warning duplicated across tests) - #149739 (mailmap: add binarycat) r? `@ghost` `@rustbot` modify labels: rollup
rust-timer
added a commit
that referenced
this pull request
Dec 8, 2025
Rollup merge of #149736 - dawidl022:contracts/chore/cleanup-warning-in-tests, r=Kivooeo,jieyouxu contracts: clean up feature flag warning duplicated across tests There is no need for every contracts test to assert the same warning for using the `contracts` feature flag, as such use `#![expect(incomplete_features)]` in the tests, and add one test to specifically check for the warning. Making this change has been discussed in the comments of #149722. Contracts tracking issue: #128044 r? Kivooeo
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.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
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.
There is no need for every contracts test to assert the same warning for using the
contractsfeature flag, as such use#![expect(incomplete_features)]in the tests, and add one test to specifically check for the warning.Making this change has been discussed in the comments of #149722.
Contracts tracking issue: #128044
r? Kivooeo