-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
const-eval: always do full typed copies #149901
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
base: main
Are you sure you want to change the base?
Conversation
|
@bors try |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
const-eval: always do full typed copies
This comment has been minimized.
This comment has been minimized.
|
The job Click to see the possible cause of the failure (guessed by this bot)For more information how to resolve CI failures of this job, visit this link. |
|
Queued db4e1d2 with parent 5b150d2, future comparison URL. |
Perf experiment exploring alternatives to #148967.
This is the maximally naive version that just always does full typed copies. It may be possible to skip some of the validation work if all we care about is resetting padding -- though it's not obvious to me how to do that in a way that actually helps with performance. Also, typed copies at integer type technically do not preserve provenance, which could become relevant in const-eval for the same reason as provenance in padding (see #148470) -- so it's not like we can just skip all types without padding.