Belated thanks, I *hope* this is fixed in the latest build if you're interested. I actually think this was an erroneous fallthrough -- the TLDR is that I had a "return;" inside a loop when it should have been outside. I had a lot of work to do with the hints. It feels like there might be some special cases still to knock out, but this one seems fixed.