- is this problem now fixed?
- if not, what is the fix?
does anyone wish to overturn the status quo?
- do we allow peeking on unbuffered input port?
- should strings be immutable?
- should string-set! be in a separate library?
- should we flush string-ref?
- should we add string-for-each?
- if not, what kind of entity does string-ref return?
- should we require variable-length strings?
- should we allow direct creation of custom text ports?
make-hash-table hash-function and equiv procs must not mutate hash-table?
shall we reject all three suggestions?
23. allow inline hex escapes anywhere?
- or "allow anywhere except within a hex escape"?