try @allocated
changes on 1.12
#59532
Draft
+94
−24
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.
This is to see how this change affects 1.12 PkgEval. Note we do not expect 100% compatibility for this, because number of allocations is implementation-dependent and not part of the API. Here I want to (1) restore the scope behavior for complex expressions, (2) try to avoid spurious allocations from call sites, and (3) failing that, make the behavior more predictable so tests can be updated more easily if they break.
@nanosoldier
runtests(ALL, vs = ":release-1.12")