TR: inconsistent type errors, part 1
Open
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 575
- Forks
- 106
- Avg merge
- 2h 1m
- Merged PRs (30d)
- 2
Description
Resubmission of PR15163 in github.
- Open two tabs in DrR, both with
#lang typed/racket. - In the first, add
(map rest '((1)))as a second line. - Run both.
- In the interactions window of the second, enter the same
expression on the REPL.
Now compare the two type errors: the one with the expression in the file
has "Types" with output type specified and an "Expected result". The
REPL one has just "Domains" (no output types) and no "Expected result".
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
Reproduce the discrepancy in DrR with two #lang typed/racket tabs, using (map rest '((1))) in a file and in the second tab's REPL. Compare the reported Types, Domains, and Expected result sections; done means both contexts present consistent type-error information.
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