racket / racket/typed-racket

mysterious error message when referencing bindings from untyped rackunit

Open
#989 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Racket
Stars
575
Forks
106
Avg merge
2h 1m
Merged PRs (30d)
2

Description

What version of Racket are you using?

racket cs: 7.9.0.3 on 3db7e471eb605fece59609b26e4212456a12878f
typed racket on f5128a51abfe13a0bebbf1635c622261367e58ea

What program did you run?
#lang typed/racket
(module+ test
  (require rackunit)
  (check-equal? 1 1))
What should have happened?

something like:

Type Checker: missing type for identifier;
 consider using `require/typed' to import it
  identifier: check-equal?
  from module: rackunit.rkt

or better:

Type Checker: missing type for identifier.
 identifier: check-equal? 
 from: rackunit.rkt
consider one of the following options: 
  1. import it from`typed/rackunit`
  2.use `required/typed` to import it 
If you got an error message, please include it here.
Type Checker: missing type for identifier;
 consider using `require/typed' to import it
  identifier: provide/contract-id-syntax->location
  from module: location.rkt
  in: provide/contract-id-syntax->location
  context...:
   /Users/capfredf/code/racket-extra-pkgs/typed-racket/typed-racket-lib/typed-racket/typecheck/tc-toplevel.rkt:376:0: type-check
   /Users/capfredf/code/racket-extra-pkgs/typed-racket/typed-racket-lib/typed-racket/typecheck/tc-toplevel.rkt:619:0: tc-module
   /Users/capfredf/code/racket-extra-pkgs/typed-racket/typed-racket-lib/typed-racket/tc-setup.rkt:96:12
   /Users/capfredf/code/racket-extra-pkgs/typed-racket/typed-racket-lib/typed-racket/typed-racket.rkt:23:4

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

Reproduce the typed/racket program from the issue, then start with the type-checking path in typed-racket/typecheck/tc-toplevel.rkt and the referenced location.rkt behavior. Compare the reported identifier with the expected check-equal? diagnostic and verify that the error points to the user-facing binding with actionable import guidance.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.