Refactor MonadSodium into MonadMLock etc. #388
Closed
Conversation
This file contains 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
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 acknowledges the fact that by now, the MonadSodium typeclass is not really about libsodium anymore, and has become a kitchen sink of various concerns that we needed to abstract over in order to use mlocked memory and related functionality. Hence, we split up
MonadSodiuminto a set of orthogonal typeclasses, each covering one of those concerns.Specifically, the new typeclasses we introduce to replace
MonadSodiumare:MonadMLock, covering mlocked memory operationsMonadByteStringMemory, covering access to raw memory in bytestrings (Data.ByteString.useAsCStringetc.)MonadPSB, covering thePinnedSizedBytesAPIMonadUnmanagedMemory, covering memory allocations/deallocations outside of the Haskell heap (allocaBytesetc.)