racket / racket/drracket

Error in guide does not appear with DrRacket defaults

Open
#571 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

What version of Racket are you using?
e.g., 8.5 [cs]

What program did you run?

image

(module just-lambda racket
(provide lambda))
(module identity 'just-lambda
(lambda (x) x))

(no error message)

from https://docs.racket-lang.org/guide/module-languages.html#%28part._implicit-forms%29

What should have happened?

an error message as depicted in the guide

image image

module: no #%module-begin binding in the module's language in: (module identity (quote just-lambda) (lambda (x) x))

Please include any other relevant details

the drracket default is for debugging to be on - this causes error trace to provide #%module-begin so the error does not display as depicted in the guide.

Options

  1. Add a callout to explain the behaviour
  2. change the behaviour of the debugging modes(errortrace) to provide the expected error?

I'm happy to do (1) as a temporary measure, but I am unable to do (2)

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 reviewing the guide's module-languages.html#%28part._implicit-forms%29 section and reproducing the example in DrRacket with its default debugging and errortrace settings. Compare the observed output with the documented error, then determine whether the guide should explain the behavior or the default behavior should change; done means the discrepancy is resolved and verified.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.