racket / racket/redex

Internal contract violation when using `generate-term` that should satisfy a target judgement

Open
#75 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
112
Forks
42
PR merge metrics
No merged PRs in 30d

Description

I am currently trying to implement Featerweight Java in PLT Redex, and I am getting the following error:

[...]/generate-term.rkt:825:9: error: contract violation
  expected: (or/c string? symbol?)
  given: #<procedure:resolve-no-nts/pat>
  argument position: 1st
  other arguments...:

when calling

(generate-term FJ #:satisfying
                    (well-formed () (L P))
                    10)

It seems to work well when using just

(generate-term FJ (L P) 10)

so I would guess the issue is intrinsic to the #:satisfying form.

The complete code is available here in this Gist:
https://gist.github.com/ahmadsalim/e3b0359e8a81e89aa7089b9e82a52f09 .

Any idea on why this error occurs, and whether it is possible to fix it?

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Run the complete reproduction from the linked Gist, then inspect generate-term.rkt around line 825 and trace the #:satisfying path that produces the contract violation. Done means the shown (generate-term FJ #:satisfying ...) call completes without the error while the ordinary generate-term form continues to work.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.