Repository navigation
Conversation
|
I'm not sure if this is the best solution. It takes an extra Maybe instead we could store the original parent array and index in that? This item was found at this index of this source array. Then that's just known, there's no need to rely on |
Weirdly, I'm not able to reproduce this exact exception on a variety of targets that I tried. Most targets seem to throw no exception at all for me. I'm getting a SIGNAL11 from HashLink, though. No message with it. However, it does appear to be caused by the -1 index. I can see that the logic is a bit wonky here. The call to I'll look into cleaning this up when I get a chance. |
|
Closing this because I plan to submit a better solution as part of the other PR. |
Without this, the following will crash because it can't find the original item.
I was trying to prove it'd write to the unfiltered
[1, 1]location, but it didn't even get that far.