feat: remove all unsafe code from the project - #55
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I was nerdsniped by #47 and went ahead and removed all the unsafe code in the repo without adding runtime unwraps. Well...without adding any new runtime unwraps. In reality, both of these were handling the NonZeroU32 was 0 case -- I just rerouted them such that they didn't do a new unwrap.
https://godbolt.org/z/n8Teha5Gc
We have two cases of unsafety:
Generation::nextandFreePointer::from_slot.Generation::next's new safe-only implementation produces the exact same bytecode.Interestingly,
FreePointer::from_slotis now faster while being safe -- we lost one single instruction in the new method. Surely that'll be massive percentage increases in speed!In all reality, these are minor tweaks with syntax.