OK. I'd like to cover the other features too.
How about signalling a tg:unsupported-weak-operation error? Would that work for your use case? This would be similar to the current mode of operation (except we currently signal a generic simple-error).
Cheers, Luís
On Tue, Jul 30, 2019, 2:12 AM Name Here theemacsshibe@gmail.com wrote:
Yes, we're trying to factor out the implementation-specific code so that only trivial-garbage needs to be updated for new implementations with weak pointers, but we also want Flexichain to mostly work if the implementation does not support weak pointers, falling back to strong pointers in that case.
Sure, that would be great too.
On Wed, Jul 31, 2019 at 12:05 AM Luís Oliveira luismbo@gmail.com wrote:
OK. I'd like to cover the other features too.
How about signalling a tg:unsupported-weak-operation error? Would that work for your use case? This would be similar to the current mode of operation (except we currently signal a generic simple-error).
Cheers, Luís
On Tue, Jul 30, 2019, 2:12 AM Name Here theemacsshibe@gmail.com wrote:
Yes, we're trying to factor out the implementation-specific code so that only trivial-garbage needs to be updated for new implementations with weak pointers, but we also want Flexichain to mostly work if the implementation does not support weak pointers, falling back to strong pointers in that case.
trivial-garbage-devel@common-lisp.net
-
Luís Oliveira -
Name Here