> For example, in implementations where the filename of the library
> definition depends on the library name, every alias would need a new
> file, which just consists of one line.

Gauche and Chibi currently do it that way.

> It would be more economical if
> there was just one table (some sexp file) that holds the alias
> mappings. Or, maybe, one file per directory. This could be
> semi-standardized for those implementations that work on the file
> system.

True. I like this idea.

This would tie neatly into my SCHEME_PATH proposal, where SCHEME_PATH is
a list of directories and each directory can have a `meta.scm` (name up
for debate) with metadata about how to look up libraries in that directory.