feat: Bitstring encodings - #21
Draft
BoltonBailey wants to merge 2 commits into
Draft
Conversation
Resolve conflicts with the module-system migration: migrate the new Encoding files (Delimit, Bitstring, Encoding aggregation) to module style with public imports and @[expose] public section, add the Encoding import to the root module, and drop List.append_assoc simp args made unused by pair unfolding through delimit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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 PR adds bitstring encodings, trying to make it a bit more natural to express e.g. polytime computability on arbitrary input types.
As a part of this it refactors the "delimiting" operation out of the current definition of
pair, to reuse for other typeclass derivations.