Browse Source
An oversight in the implementation of J and Y meant that the chain would grow each frame, if there were at least two segments and the first segment was locked by something like H. Example: H YY This is not what we want. I've added a guard in the J and Y implementations that checks if the glyph above (or for Y, to the left) is an earlier part of the chain, and if it is, to return. This has the downside of making long chains potentially having to enter the J code repeatedly, only to end up doing nothing. The STUN() in J and Y might no longer be worth it. It was used to prevent further operators in the chain from running, but since we have a guard now, the writes while looping might end up costing more time. We don't have any good benchmark files set up right now, so we'll have to test it in the future.master

1 changed files with 8 additions and 4 deletions
Loading…
Reference in new issue