Allocator-aware @safe reference counting is still not possible
Paul Backus
snarwin at gmail.com
Mon Jan 30 18:49:19 UTC 2023
On Monday, 30 January 2023 at 18:33:57 UTC, Richard (Rikki)
Andrew Cattermole wrote:
> If we hired some people then yes 1&2 (but not 3). Otherwise we
> are stuck with changing the goal posts from perfect to good
> enough for the time being. As Andrei use to say: perfect is the
> enemy of the good; which is unfortunately what I think we need
> to strongly consider here. We have what appears to be a pretty
> decent path forward for 'good'.
I'm not opposed to the idea of moving the goalposts in principle,
I am just not sure where you are proposing that we move them to.
:) It seems like every time I ask, I get a different answer.
> It shouldn't matter what allocator library you use. Either it
> works or it doesn't. The compiler shouldn't care whose code it
> is, only the lifetime patterns.
For example: I agree with this paragraph in principle, but isn't
this one of the goalposts that you were just saying we should be
willing to move?
More information about the Digitalmars-d
mailing list