Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[sequences] no memory -> partial memory #368

Merged
merged 1 commit into from
Jan 1, 2023
Merged

Conversation

stonier
Copy link
Member

@stonier stonier commented Jan 1, 2023

  • restart the sequence, but allow children to retain their state
  • invalidate any potential dangling runners if the sequence halts mid-way

Resolves #329.

(apologies, this was a long time in coming)

@stonier stonier merged commit 1c647ea into devel Jan 1, 2023
@stonier stonier deleted the stonier/sequences branch January 1, 2023 16:26
@stonier
Copy link
Member Author

stonier commented Jan 1, 2023

There is a followup to this that provides eliminates the inconsistency in default settings for memory between Selector and Sequence#370.

NB: PR 370 goes further to enforce explicit argument configuration for composites - it should help ease a transition and ultimately make composite code a little more introspectable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Semantics of sequence without memory are wrong
1 participant