You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should consider removing the "global" ManipulatorInfo from CompositeInstruction and prefer for each PlanInstruction to maintain its own instance of ManipulatorInfo. This should reduce confusion about which instance of ManipulatorInfo is higher priority.
We could create a function that applies a ManipulatorInfo to all PlanInstructions within a CompositeInstruction, like:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We should consider removing the "global"
ManipulatorInfo
fromCompositeInstruction
and prefer for eachPlanInstruction
to maintain its own instance ofManipulatorInfo
. This should reduce confusion about which instance ofManipulatorInfo
is higher priority.We could create a function that applies a
ManipulatorInfo
to allPlanInstruction
s within aCompositeInstruction
, like:Beta Was this translation helpful? Give feedback.
All reactions