feat: Derive Arbitrary instances for inductive datatypes.#41
Merged
hargoniX merged 1 commit intoleanprover-community:mainfrom Oct 15, 2025
Merged
feat: Derive Arbitrary instances for inductive datatypes.#41hargoniX merged 1 commit intoleanprover-community:mainfrom
hargoniX merged 1 commit intoleanprover-community:mainfrom
Conversation
codyroux
commented
Oct 2, 2025
fe046cc to
5dcf39e
Compare
Contributor
Author
|
@ngernest, do you want to take a quick look? |
|
@codyroux This looks good to me, thanks! |
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.
WIP: this is a re-do of PR #35, mostly unchanged but for breaking the
ArbitraryFuledclass out.I'm actually now convinced that we might want a fueled class in addition to
size: e.g. for tree-like structures, the number of nodes is exponential in the depth at the moment. Is this the behavior we want? If so, then we want to keep size small but perhaps allow fuel to be large. If we switchsizeto correspond to the number of nodes, then now fuel has to be huge if we generate many things.For now though, we should always be generating total functions, so fuel should be relatively moot. I can try to remove it if we feel that it is a distraction.