racket / racket/typed-racket

errortrace throws an error with imported submodules

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

Nobody has claimed this yet.

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

Description

What version of Racket are you using?

6.12

What program did you run?
#lang errortrace typed/racket

(module a typed/racket
  (provide a)
  
  (define a 5)
  )

(require 'a)

a
What should have happened?

The program should output 5. Instead it outputs an error.

The error goes away if #lang errortrace typed/racket is changed to #lang typed/racket, or if both uses of typed/racket are changed to the racket language.

If you got an error message, please include it here.
 reference to a module that is not available
  reference phase: 0
  referenced module: (submod 'expanded module a)
  referenced phase level: 0
  in: a
  context...:
   standard-module-name-resolver

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

Start by running the provided module example with Racket 6.12, comparing #lang errortrace typed/racket with #lang typed/racket and the racket variants. Confirm that the errortrace version reports the namespace mismatch while the expected result is 5; the issue does not name a repository file or test entry point.

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.