I strongly suggest not to do this for any API that is for inclusion
What do you suggest for the proposed file-open for SRFI 170, with its required argument "pathname" and its six other arguments? My original design used a p-list, but that loses performance on Schemes with native keywords already. Other examples are arising soon.
(I'm not arguing against using SRFI 177 to implement an API. But new
APIs definitely do not need keywords, even not to be pretty.)
R7RS-large is not about what is *needed*, nor is R7RS-small. All we *need* are lambdas, or if we must have lists, all we *need* for them is pair?, cons, car, cdr, set-car!, and set-cdr!. Remember the goals of R7RS-large from our charter: "a language that embodies the essential character of Scheme, that is large enough to address the practical needs of mainstream software development, and that can be extended and integrated with other systems."