Right now regular we do this manually, but true, this could be better to use BLI_SCOPED_DEFER
.
Hans said that nodes should have deterministic behavior, so this can be considered a bug. After a light build: the performance drop is hard to find, seems to be quite low indeed. So this is…
Just use the attributes, they already give you that, and no one will suffer performance but you.
Loop over the coordinates ordered by #KDTreeNode.index. At the expense of some performance, this ensures the layout of the tree doesn't influence the iteration order.
Not sure if…
@MMMM This is not stated in the documentation. And I can't read minds, but for some reason it seems that this was not planned. You MUST do this with attributes, since copying them alone will not…
Hello, thanks for the report. While I can confirm this behavior, it's not a bug.
This node must resize the point domain randomly and in random order. Because of this, some deterministic…