+1, also + to use static_assert
for check that type is trivia;/lock-free (not sure if this really will pretext us from non-trivial implementation of the class).
Issue is in UI handling of user input while showing tooltip and this is not limited by the nodes editor.
I'm not reallocating or overwriting anything.
You do that everytime you create new attribute.
Seems like reference devalidation.
Might be duplicate of #126286.
This can be part of this task but requires few more actions: Attribute input node and AOV Output nodes in shading. Both should behave in the same way as Attribute input and Store Named Attribute…
Issue is in the fact of using library linking which is for some reason force to access to actually evaluated IDs of materials for node tree but some other evaluated ones. For the context,…