Re: Remove parameter? in favor of SRFI 226?
Shiro Kawai 31 Oct 2026 03:43 UTC
Although I like srfi-226, I expect it'll take a long time to be widely
adopted because it's large. So having `parameter?` in a separate srfi
would be useful, as it can't be implemented without interacting with
the underlying parameter mechanism for each implementation.
We could say: "Returns true whenever object is a parameter object, as
returned by make-parameter, and false otherwise." , just to clarify.
On Fri, Oct 30, 2026 at 4:48 PM Peter McGoron <xxxxxx@mcgoron.com> wrote:
>
> I say keep it in 282.
>
> It is possible to implement a parameters with a predicate without
> implementing all of SRFI 226. I think it would be useful.
>
> SRFI 226 says “The parameter objects defined in this specification are
> fully compatible with the parameter objects of SRFI 39 and R7RS…,” SRFI
> 226 parameter? should be compatible with 282 parameter?.
>
> -- Peter McGoron
>