Sometimes I want to do operations like calculating the average of an attribute value, but I don't want to change the attribute class.
Is there a faster and more efficient way than using two attribute promote nodes? (One to promote to a different class and do the calculation, and another one just to convert the attribute class.)

Is there a reason the attribute promote should not be able to “promote” to the same attribute class?

I wrote an operator called Attribute Unify that does this operation in VEX. It's pretty involved because it doesn't just use the whole geometry but either connectivity with depth control or point cloud method.

Both methods involve creating intermittent geometry that represents their relationship/proximity with each other separately for points and primitives.

I will upload my version to Orbolt sometime.

But if you just want the promote the whole geometry i.e. all points, prims, etc 2 Attribute Promote SOPs are the best way I think.

Cool thanks!