This page is part of the web mail archives of SRFI 14 from before July 7th, 2015. The new archives for SRFI 14 contain all messages, not just those from before July 7th, 2015.
The functions predicate->char-set and char-set-invert[!] can take a long time if you define char-sets on a Unicode system (which you can do on Gambit-C), especially if you follow the suggestion in the body of the proposal: "Large" character types, such as Unicode, should use a sparse representation, taking care that the Latin-1 subset continues to be represented with a dense 32-byte bit set. So, are these really necessary? Should we omit them? Brad