Comment by klez
13 hours ago
I hope you don't take this question the wrong way: why is R7RS large taking so long? Is there a consensus problem or just a lack of resources? If it's the latter, is there any way a random scheme dabbler can help?
13 hours ago
I hope you don't take this question the wrong way: why is R7RS large taking so long? Is there a consensus problem or just a lack of resources? If it's the latter, is there any way a random scheme dabbler can help?
The committee needs to think long and hard about which features to propose in each docket and what those features should look like, a lot of discussion needs to take place in order to get each docket formed, then the wider public needs to get its chance to weigh in, and then a voting round needs to be held. That process may need to happen several times for a docket, and there's a bunch of dockets planned before R7RSL will be done.
Think of it this way: if the committee was more cavalier about this we'd have the familiar situation where we start with a great language and then every update worsens it until we end up with an abominable horror show.
What tmtvl said is correct. However, it is also a resource problem. R7RS Large is a volunteer driven effort where if people stop having the time to contribute due to personal reasons, things slow down.
> If it's the latter, is there any way a random scheme dabbler can help?
Giving your comments on drafts, issues[1], and draft SRFIs is always welcome. The decisions of the Working Group are more complete when we hear more voices.
[1]: https://codeberg.org/scheme/r7rs/issues