racket / racket/typed-racket

truly surprising error message from TR

Open
#779 4 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?

Welcome to DrRacket, version 7.0.0.20--2018-09-12(-/f) [3m].

What program did you run?

This student program:

#lang typed/racket

(define (subst [ft: BTree] [sy : Symbol] [rt : BTree])
  (match ft
    [(Node l r) (Node (subst l sy rt) (subst r sy rt))]
    [(Leaf sy) rt]
    [(Leaf s) (Leaf s)]))
What should have happened?

An error message highlighting some larger area, and text that makes a bit more sense.

If you got an error message, please include it here.

The highlighted region is the [sy : Symbol], and the error message is as follows:

define: expected more terms starting with expression
parsing context:
while parsing optional lambda argument
while parsing lambda-formals
while parsing curried-formals in: (sy : Symbol)

(yes, I see what the actual error is... but honestly, I think the only plausible way to diagnose this error is to stare at the program until you see the problem.)

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 supplied typed/racket program in DrRacket and inspect the parsing context around the optional lambda argument and curried formals. Done means the reported source region and error text make the actual malformed argument declaration easier to diagnose.

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.