racket / racket/rhombus

Some solution to the "no-value" value,

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

Nobody has claimed this yet.

Dominant language
Racket
Stars
601
Forks
74
Avg merge
2d 10h
Merged PRs (30d)
5

Description

Some solution to the "no-value" value, which could be such a blessed value, or it could be a way to say that some function accepts all the keywords as some other function. (Possibly related to the above, of course.)

from Wishlist of backwards incompatible things for a future Racket2. #33

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 reading this issue together with the referenced “Wishlist of backwards incompatible things for a future Racket2” issue (#33). The issue proposes a solution for a “no-value” value or a way for one function to accept all keywords accepted by another, but does not identify files, tests, or an implementation boundary. Done would require a decided design and an agreed implementation scope.

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
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.