Hi Marc, hi list,

I read in srfi-254, about ephemeron:
------
If the content of an ephemeron's key field denotes a location or a
sequence of locations, the ephemeron is broken in the course of the
computation if the garbage collector would reclaim the location or
sequence of locations if the location denoted by the ephemeron's value
field were weakly holding. The ephemeron may be broken in the course of
a computation if the Scheme implementation can prove that the location
or sequence of locations will not be kept alive in the future of the
computation if the ephemeron is broken.
-----

I also read, about reference-barrier:
-----
If obj is an object such as a pair, string, vector, or bytevector that
denotes a location or a sequence of locations, the location or the
sequence of locations is kept alive.
-----

In both case, I don't understand what describes and expects srfi-254.
But I cant easily understand what srfi-124 describes and expects.

So in my opinion if srfi-254 has to superseed srfi-124, some rewording
must occur.

I didn't checked for srfi-246.

regards
José