[feature request] Clarify when `redex-check` generation fails because `#:prepare` returns a bad term
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 112
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes the argument to #:prepare will return a term that doesn't match the input pattern, which causes generation to fail.
Usually, for me at least, this is an error. Ideally it would be nice to be able to configure redex-check to error when this happens, but it might also be good change the message (with Y generation failures) to something like (with X generation failures, Y of which were caused by prepare) or something.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the redex-check entry point and the handling of #:prepare results. Determine how generation failures are currently counted and reported; done means prepare-caused failures are clearly distinguished and the requested error behavior is configurable.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100