Could srfi-128 "basic" comparators, to be the basis of various 
containers, and a separate utility library that contains other fluffs? 
If we don't have the revisions such as in hash function signature, we
might even be able to keep srfi-114 as the optional enhanced 
comparator library while srfi-128 being essential base.

Because of the changes, I think we could say srfi-114 will evolve
into srfi-128 basic comparators and srfi-xxx comparator utilities, or something.

I did implement the basic comparators as Gauche built-in so that other
built-in containers can use it, and left other utility stuff into a separate library.



On Wed, Oct 28, 2015 at 3:51 PM, John Cowan <xxxxxx@mercury.ccil.org> wrote:
Kevin Wortman scripsit:

> For what it's worth, I don't really see what's wrong with SRFI 114. I've
> been implementing finger trees on top of SRFI 114 comparators, and the
> comparators seem to work fine.

I've gotten feedback that it's too large and hairy for a core Scheme
component that is required to make use of sets and possibly hash tables.

--
John Cowan          http://www.ccil.org/~cowan        xxxxxx@ccil.org
As you read this, I don't want you to feel sorry for me, because,
I believe everyone will die someday.
               --From a Nigerian-type scam spam