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

Migrate ctfe-stress-test-3 to ctfe-stress-test-4 #552

Merged
merged 1 commit into from
Nov 12, 2019
Merged

Migrate ctfe-stress-test-3 to ctfe-stress-test-4 #552

merged 1 commit into from
Nov 12, 2019

Conversation

davidhewitt
Copy link
Contributor

If rust-lang/rust#66294 lands then evaluation of const fn with no arguments will be memoized. This breaks the purpose of the tests in ctfe-stress-3.

This PR changes to a new ctfe-stress-test-4 which is identical save that the const functions now take a dummy u32 argument to avoid memoization.

r? @oli-obk

If rust PR #66294 lands then evaluation of `const fn` with no arguments
will be memoized. This breaks the purpose of the tests in ctfe-stress-3,
so this PR changes to a new ctfe-stress-test-4 which is identical save
that the const functions now take a dummy u32 argument to avoid memoization.
@oli-obk
Copy link
Contributor

oli-obk commented Nov 12, 2019

@bors r+

@Mark-Simulacrum
Copy link
Member

Does it make sense to keep around a memoized case (though maybe smaller) so we can detect if memoization regresses in the future?

@oli-obk
Copy link
Contributor

oli-obk commented Nov 12, 2019

We already test the memoization in the rustc test suite by causing cycles on recursion

@Mark-Simulacrum
Copy link
Member

Okay, great!

@Mark-Simulacrum Mark-Simulacrum merged commit ea56a34 into rust-lang:master Nov 12, 2019
@davidhewitt davidhewitt deleted the ctfe-stress-test-4 branch November 12, 2019 19:47
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.

3 participants