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

staticdata: make completeinfo memory-/gc-safe #48832

Merged
merged 1 commit into from
Mar 1, 2023
Merged

Conversation

vtjnash
Copy link
Sponsor Member

@vtjnash vtjnash commented Feb 28, 2023

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.

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.
@vtjnash vtjnash added the backport 1.9 Change should be backported to release-1.9 label Feb 28, 2023
@vtjnash vtjnash requested a review from timholy February 28, 2023 21:23
@vtjnash vtjnash added the merge me PR is reviewed. Merge when all tests are passing label Feb 28, 2023
@N5N3 N5N3 merged commit 0608824 into master Mar 1, 2023
@N5N3 N5N3 deleted the jn/safe-staticdata-info branch March 1, 2023 01:10
@N5N3 N5N3 removed the merge me PR is reviewed. Merge when all tests are passing label Mar 1, 2023
@KristofferC KristofferC mentioned this pull request Mar 3, 2023
50 tasks
vchuravy pushed a commit that referenced this pull request Mar 3, 2023
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 pushed a commit that referenced this pull request Mar 3, 2023
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 pushed a commit that referenced this pull request Mar 3, 2023
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)
KristofferC added a commit that referenced this pull request Mar 6, 2023
@KristofferC KristofferC mentioned this pull request Mar 7, 2023
52 tasks
@KristofferC KristofferC removed the backport 1.9 Change should be backported to release-1.9 label Mar 31, 2023
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.

4 participants