Open
Conversation
…' into pr/feature-requests
…oc regarding extensionality
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
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.
Issue #, if available:
Description of changes:
Summary
This PR brings the Boole feature-request suite, working examples, and documentation back into sync with the current state of the Boole pipeline.
It updates both the implementation and the example/backlog story so the repo more accurately reflects what is supported today versus what is still an open request.
Main changes
Maptypes via=~=, lowering it to an explicit quantified formula during translation.forlowering end to end by:forloopssquare_matrix_multiplyis now a main working Boole examplestring_operatorsis now a main working Boole examplehorner_poly_evalremains a feature-request seedbinary_searchwas removed#guard_msgssnapshotssmtVCsCorrectproofs where appropriatedocs/BooleFeatureRequests.mdso it now:Sourcecolumn showing where each seed came fromBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.