use GC.malloc_atomic to allocate objects without pointers #4081
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.
bdwgc recommend to use malloc_atomic (https://github.com/ivmai/bdwgc#the-c-interface-to-the-allocator) to allocate binary data. I apply this to some places, but there is actually much more places, that can be optimized.
Bytes.new
for example, or betterPointer(T).malloc
choose to use atomic if T is not reference.