Skip to content

Conversation

@dickhardt
Copy link
Collaborator

No description provided.

@dickhardt
Copy link
Collaborator Author

addresses issues #20 #7

@gffletch
Copy link

At a high level... I'll just record my meta issue here. As we add async processing it feels like there is more and more overlap with shared signals. I would love to see a way to enable the same "command set" over the shared signals framework though that will end up meaning we have two ways to do the same thing.

@dickhardt
Copy link
Collaborator Author

A shared signal specification for the same command semantics seems like it would be useful.

@gffletch Is there something in how this is structured that would not enable shared signals to have something equivalent semantically?

@dickhardt dickhardt merged commit e50c369 into main May 21, 2025
1 check passed
@dickhardt dickhardt deleted the async-commands-and-callbacks branch May 21, 2025 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants