Skip to content

[EXPERIMENTAL] try a workaround for unstable error message order #128505

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

Closed

Conversation

folkertdev
Copy link
Contributor

in #125558 we're running into error messages being printed in a different order on different machines. This PR tries to separate the tests into multiple files, so hopefully that is no longer a problem. Not a great solution, but it would get us unstuck.

r? @ghost

Amanieu and others added 7 commits July 25, 2024 20:12
Previously these would be treated like integer literals and default to
`i32` if a type could not be determined. To allow for
forward-compatibility with `str` constants in the future, this PR
changes type inference to use an unbound type variable instead.

The actual type checking is deferred until after typeck where we still
ensure that the final type for the `const` operand is an integer type.
Co-authored-by: Amanieu d'Antras <[email protected]>
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Aug 1, 2024
@rust-log-analyzer

This comment has been minimized.

@folkertdev
Copy link
Contributor Author

this has served its purpose

@folkertdev folkertdev closed this Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant 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.

4 participants