Skip to content

Detect when a record, tuple, or call can write in-place #1002

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
marijnh opened this issue Oct 4, 2011 · 1 comment
Closed

Detect when a record, tuple, or call can write in-place #1002

marijnh opened this issue Oct 4, 2011 · 1 comment

Comments

@marijnh
Copy link
Contributor

marijnh commented Oct 4, 2011

If you do x = rec(a=10 with x) or y = f(y) or similar, the result has to be constructed in a scratch space, rather than directly into the local variable's memory, because the local is needed to build the result. The alias analysis could mark expressions where this is not needed, so that we can avoid this scratch alloc + move as much as possible. (This is already done when the expression initializes the memory, rather than replacing an existing value.)

@ghost ghost assigned marijnh Oct 4, 2011
@marijnh
Copy link
Contributor Author

marijnh commented Feb 28, 2012

I'm going to close this. Doing it correctly turned out to be harder than expected, and the win wouldn't be that big.

@marijnh marijnh closed this as completed Feb 28, 2012
@marijnh marijnh removed their assignment Jun 16, 2014
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
…t-lang#1002)

* Replace cprover_Asserts

* Add Tests for Property Classes
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

No branches or pull requests

1 participant