On 5/26/24 09:01, Nathaniel Shead wrote:
Is this approach OK? Alternatively I suppose we could do a deep copy of
the overload list when this occurs to ensure we don't affect existing
referents, would that be preferable?
This strategy makes sense, but I have other concerns:
Bootstrapped and
Is this approach OK? Alternatively I suppose we could do a deep copy of
the overload list when this occurs to ensure we don't affect existing
referents, would that be preferable?
Bootstrapped and regtested (so far just modules.exp) on
x86_64-pc-linux-gnu, OK for trunk if full regtest succeeds?
