schemers | Let 's build a scheme interpreter in Rust | Interpreter library

Your goals are contradictory. If s is a stack, and your operations purely functional, then (s 'push 1) must return the same thing every time it is called. To capture the notion of change, you must use a different s each time. That's how your functional stack works: it gives you back a new stack, and you must compose function calls with it.

The honest answer is probably "no" - there is not a single version of srfi preferred by the community.

But to (kinda) answer my own question, whilst I can't say it's a defacto standard yet, Akku is a package manager and virtual environment management system of Scheme that is miles ahead of any of the alternatives, and actively developed. It's not an individual implementation of srfi, but is a way to install various Scheme packages you need to use through a single interface.

https://akkuscm.org/

It's not quite venv and pip - but it's getting there. I'm amazed this isn't talked about more, I only stumbled upon it some time after my initial search for a tool like this.

You get a single interface to pull packages for both R6RS and R7RS, and a range of Scheme implementations.

There is also Snow, which is currently only supporting R7RS: http://snow-fort.org/

But as Akku mirrors Snow as well as providing R6RS support, it is more comprehensive.

To answer the specifics of the original example - Akku installs chez-srfi by default (on a Chez Scheme system at least) on creation of a new project, but also offers thunderchez as a package. Whether that indicates a preference by the Akku developer's, I'll leave up to the reader to decide.

The original question was about a single defacto srfi implementation for Chez, rather than a more general package manager. In hindsight this misses the point a bit, simply because I didn't think a single package manager (beyond srfi) was a remote possibility.

So for my use at least - Akku, not only provides various implementations of srfi, but also offers a host of other packages, and largely answers my question.

Yes. It is very non lispy that we have a modifier ... that changes the meaning of element in front. eg. something ... is basically similar to . something except it works with structures like this:

This is Chibi's implementation:

• remainder: https://github.com/ashinn/chibi-scheme/blob/master/bignum.c#L527

• modulo: https://github.com/ashinn/chibi-scheme/blob/master/lib/init-7.scm#L1398

The author is one of the authors of R7RS.

This is a remarkably subtle example. In the first example:

Why did the authors of plt-r5rs not define the error procedure?

It appears that The Revised⁵ Report on the Algorithmic Language Scheme does not define a procedure named error. The initial environment created by plt-r5rs contains only the values and syntactic forms defined in the report (except for a handful of implementation-specific forms listed in the docs, like #%require, which are not legal identifiers according to R⁵RS).

How can I define or import an error procedure so that my program can run? Perhaps there's a way to import SRFI-23 Error reporting mechanism?

As you probably know, R⁵RS also does not define a module system, so there is no portable way to import anything. For plt-r5rs specifically, this version of your program works:

This notation for optional arguments is not only used here. It is also used in Unix program usage.

CHICKEN does not ship with SRFI 90, and as far as I can tell so far nobody has made an egg for it, either. An earlier and more commonly used hash table library, SRFI-69, is part of core, though. It is also not available by default, you'll need to use it like so:

I think you are using array of dictionary for your response in this line -