This is detail of realization. You shouldn’t thinking about this. And solving of this kind of cases
implementation details of attributes too.
This approach
can have problem in case there is single value is still field but not explicit (See Geometry Nodes: Simulation nodes not work with sampling nodes if value is single).
Main goal of single value fields, as i can see, is just make more explicit operation on non-field things. Trying to optimize this…?
But the very essence of the question has a problem. Users should not attempt this. It is not up to the user to determine where a group of nodes should make a field, but where a sing value. It depends on how well the field system is optimized.
Case simulations have a different problem:
Fields cannot live long. They should always evaluate to an attribute or single value if the fields are single.
But if this usually happens implicitly, then in the simulation the user must determine this himself.
In my opinion, the best thing to do here would be to simply expect the sim zone to deduce the status better (field or single). And in the interface, if it is not a field (single), the field settings for simulation sockets item should not be displayed.
This is just misleading.
