[release-1.9] Backport #48751 and #48832 #48881
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
vchuravy
commented
Mar 3, 2023
vchuravy
commented
- staticdata: make hookup of code instances correct (staticdata: make hookup of code instances correct #48751)
- staticdata: make completeinfo memory-/gc-safe (staticdata: make completeinfo memory-/gc-safe #48832)
|
Need to fix authorship on one of the commits |
vtjnash
approved these changes
Mar 3, 2023
vchuravy
force-pushed
the
vc/backports-1.9
branch
from
d2a4096 to
cb21123
Compare
There is actually almost no cases where `jl_alloc_svec_uninit` is safe, since if was safe, you would likely would prefer to use the `jl_svec` constructor instead. (cherry picked from commit 0608824)
vchuravy
force-pushed
the
vc/backports-1.9
branch
from
cb21123 to
c1cb058
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.