Make RFC about module paths, including insane submod packing idea
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 601
- Forks
- 74
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
In Racket 1, there are some strange rules about module paths. For example a refers to a/main, but a/b doesn't refer to a/b/main if a/b is a directory. I also find it awkward that a/b/c is different than (submod a/b c). It feels like it is exposing the "implementation" of b.
In Racket 2, I'd like a a/b/c is like a search path that refers to a/b/c/main.rkt (or index, or something similar), a/b/c.rkt, (submod a/b c), (submod (submod a b) c), whichever exists first.
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
The issue names no files, tests, or entry points. Start by reviewing the module-path examples and proposed lookup alternatives in this issue; done means producing an RFC that clearly documents the chosen module-path and submodule behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100