feat: expose the public PFunctor module surface - #114
Open
dtumad wants to merge 5 commits into
Open
Conversation
dtumad
marked this pull request as ready for review
August 12, 2026 01:22
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.
Summary
PFunctor.Handlerinstrumentation API for lifting handler targets and inserting pre/post effectsMotivation
Lean's module system gives
privateand unexposed declarations stronger API-boundary meaning. This change makes the intended downstream surface explicit in PolyFun so clients can depend on public laws instead of usingimport allor relying on implementation details.Validation
lake buildgit diff --checkDownstream
This is the PolyFun side of a paired change. Verified-zkEVM/VCVio#511 pins this commit and exercises the new generic
PFunctorsurface; that draft is stacked on Verified-zkEVM/VCVio#510.