Remove a 'unsafeCoerce' from 'Unsafe.coerce'#330
Merged
Conversation
Previously, the linear `Unsafe.coerce` was implemented using two `unsafeCoerce`'s, one to get a function `a -> b`, and another one to cast that function to be a linear one. After the unsafe equality proofs change[1], we have a `unsafeEqualityProof` function to cast two types to be the same without looking at the value, so we can linearly return it, removing the need for the outer `unsafeCoerce`. This removes one allocation from the generated STG code for 'Data.Array.Unlifted.get', improving the performance slightly. [1]: https://gitlab.haskell.org/ghc/ghc/-/commit/74ad75e87317196c600dfabc61aee1b87d95c214
utdemir
commented
Jun 11, 2021
| coerce a = | ||
| case NonLinear.unsafeEqualityProof @a @b of | ||
| NonLinear.UnsafeRefl -> a | ||
| {-# INLINE coerce #-} |
Contributor
Author
There was a problem hiding this comment.
This INLINE actually does not have an effect on my test case, since GHC already was inlining it even without. But I thought it's better to be explicit.
aspiwack
approved these changes
Jun 11, 2021
Contributor
Author
I didn't give too much detail :). It does help the benchmarks but only a little bit. I saw that there ends up being one less allocation on |
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.
Previously, the linear
Unsafe.coercewas implemented using twounsafeCoerce's, one to get a functiona -> b, and another one to cast that function to be a linear one.After the unsafe equality proofs change, we have a
unsafeEqualityProoffunction to cast two types to be the same without looking at the value, so we can linearly return it, removing the need for the outerunsafeCoerce.This removes one allocation from the generated STG code for
Data.Array.Unlifted.get, improving the performance slightly.