Conversation
aspiwack
approved these changes
Jun 10, 2021
Member
aspiwack
left a comment
There was a problem hiding this comment.
Always happy to remove an Unsafe.toLinear!
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.
This simple change both looks nicer, and also speeds up
one of my (yet unpublished) local benchmarks considerably.
I think calling
toLinearis very costly, since thecoercedoes not inline and the parameter to it ends up being an allocation.
Surely my terminology here is not quite right, and I would love to
know more about how the
coerceis handled on the simplifier andcore prep, so please do correct me.