Establish boundary between rhombus/racket code and platform code
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 601
- Forks
- 74
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
In order to make implementing Racket/Rhombus in other environments such as different compilers, WASM, JS, etc., all platform (i.e. calling FFI or Chez Scheme builtins) code should be explicitly called out. This should make implementing a Racket runtime in different environments easier since it would then only be required to implement these builtins plus support for full expanded Racket/Rhombus programs.
Additionally, once this is setup, adding in additional builtins in the core language should be discouraged and reusing current builtins/implementing in pure Rhombus should be highly encouraged.
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 mapping where platform calls such as FFI and Chez Scheme builtins are used, then define the boundary and identify the builtins that implementations for other environments must provide; done means platform dependencies are explicitly separated and new core builtins are discouraged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100