Can workflowcode have transient memeber variable

Can a workflow have transient field, which could be only needed for some local use (say to avoid passing to method invocation etc) .
These could be a set of fields which are just need not be persisted etc and i no way alters the state of workflow/ history etc.

I really don’t have a concrete use case but was just thinking what will be the impact of having transient, volatile fields in a workflow code.

Such fields are already fully supported. But they are still durable as the rest of the workflow state. I’d like to see a specific use case to understand if there is any limitation you are trying to solve.