Filter : Sanitise context used to evaluate Filter.enabled

[johnhaddon]

Without this, any input connections were evaluated once per location rather than just once, leading to much unnecessary pressure on the hash cache. It also provided a loophole via which you could modify the filter per location in a way that meant that ancestor and descendant matches would be inaccurate.

[johnhaddon]

Testing this with the scene where I originally noticed the problem, I'm seeing ~15% reduction in total hash count, and no appreciable change in total scene generation time.

[murraystevenson]

and no appreciable change in total scene generation time.

I also did a bit of production testing at IE today and didn't see a measurable change in scene generation time, but it makes sense to close the loophole and any reduction in hash cache pressure is a good thing.

There's a wayward comma before "made" in the Changes.md entry, but otherwise looks good to me. 👍

[johnhaddon]

There's a wayward comma before "made" in the Changes.md entry, but otherwise looks good to me.

Thanks - I've rounded up the stray, and am going to merge...