Broken Collections ancestry

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Broken Collections ancestry

Nicolas Cellier
Hi all,
I noticed a hiccup in Collections ancestry a while back (just before the lock down in France), then forgot about it, but while we are at it:

Collections-eem.883 is missing, but that's minor.

The problem is this one in trunk:

Beware, this is a false ancestor whose name conflicts with a true one
Name: Collections-eem.881
Author: eem
Time: 11 March 2020, 7:01:23.310819 pm
UUID: e9cf9901-53d5-4b5c-ab37-88beb605d007
Ancestors: Collections-eem.882

Include the Array become primitives in the ModificationForbidden framework.



Note the inversion this 881 in trunk has 882 as ancestor... A bit of a mess.
The true Collections-eem.881 ancestor of 882 is a different one:

Name: Collections-eem.881
Author: eem
Time: 11 March 2020, 6:53:50.254027 pm
UUID: 012691b6-410a-4e9a-9c64-97b5abfdba49
Ancestors: Collections-eem.880

Include the Array bulk-become machinery in the ModificationForbidden framework.


But I cannot find it anywhere. Eliot do you still have a copy of it?