Re: [Sbcl-commits] master: Make a few mostly-stylistic tweaks to macro char reading

A stable interface is a worthy goal, but more immediately, roswell is also
broken by this change (as it probably gets named-readtables from quicklisp):

https://github.com/roswell/roswell/issues/613

Waiting for a Quicklisp release can extend this pain indefinitely. Roswell
can be fixed in other ways, but named-readtables, for what it's worth, is a
low-level dependency (used by 133 thingies according to QL:WHO-DEPENDS-ON,
so maybe reverting the NIL -> 0 part of the commit would be best in the
interim?


On Mon, 10 Nov 2025 at 15:11, Douglas Katzman <[email protected]> wrote:

> I would boil this down to: I do not want to expose an iterator where I can
> provide no guarantees around how such an iterator would behave in this or
> that situation? Call it paranoia over handing out an access path to some
> internals that could fundamentally break READ without an extremely strong
> contract in place about what you'll do with the iterator, Except I also
> don't want to know what would be in that contract.
>
> Could we do instead of my previous suggestion, just (readtable-list-defined-macro-characters
> rt) that returns a list of characters currently defined to have macros ?
>

_______________________________________________
Sbcl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-devel