SRFI 279: In(tro)spection Protocol Arthur A. Gleckler (12 Aug 2026 02:50 UTC)
Re: SRFI 279: In(tro)spection Protocol Artyom Bologov (12 Aug 2026 03:09 UTC)
Re: SRFI 279: In(tro)spection Protocol Peter McGoron (12 Aug 2026 03:45 UTC)
Re: SRFI 279: In(tro)spection Protocol Artyom Bologov (12 Aug 2026 04:01 UTC)

Re: SRFI 279: In(tro)spection Protocol Peter McGoron 12 Aug 2026 03:42 UTC

Hello,

I have some general comments based off of a quick reading:

1. It might be good to have (inspect-property object property-name) so
that one can access a specific property without having to compute things
like the representation. This is nice for things like procedure
introspection, where there isn't a way to access that information otherwise.

2. Type information vs object information. Many of the property lists
(but the numbers one in particular) emit information about the type of
the object and not really the object itself. Stuff like the
smallest/largest representable value should really be in the properties
of the *type* of the object, not really the object itself.

3. How does 0..n work for circular lists?

4. Symbols are not exported from libraries, identifiers are. Symbols
wouldn't carry this type of information: (inspect-properties 'car) would
have no way of knowing that that "car" is from (scheme base) as opposed
to any other object.

5. I like the addition of procedure introspection.

-- Peter McGoron