Make an RFC about the top level
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 601
- Forks
- 74
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
We all know that "the top level is hopeless," but maybe Racket2 could be a chance to make it a little less hopeless.
The most comprehensive list of top-level issues I know is this one, but I know there have also been more mailing-list discussions in the years since. I particularly remember this thread that started with @lexi-lambda's ideas in the context of the Hackett REPL for building on submodule semantics and this one started by Christopher Lemmer Webber on their wish for a more mutable top level.
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
Start by reviewing the linked gist and the two referenced mailing-list threads, then compare their top-level concerns with Rhombus's current language design. The issue is complete when a focused RFC documents the proposed direction and addresses the cited submodule and mutable-top-level ideas.
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
- Needs clarification
- Newbie friendliness
- 25/100