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.

Sign up for GitHub

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

Jump to bottom

Error propagation #18

Closed
6r1d opened this issue Mar 3, 2021 · 1 comment
Closed

Error propagation #18

6r1d opened this issue Mar 3, 2021 · 1 comment
Labels
tidying up removing ambiguity, finding better solutions, documenting it all and adding tests

Comments

@6r1d
Copy link
Owner

6r1d commented Mar 3, 2021 •
edited
Loading

Find a way for errors to propagate correctly each time. I.e. some API mechanism.

Related: #2.

UPD: at this point I'm still in doubt on how to do that.
Currently, I am considering changing an "error queue" to "information queue" and running output ports in a duplex mode. After working a bit on #10, I am thinking that I want to know about MIDI port disconnection events fast enough. Queues sound a bit like an awkward way to handle that, but I don't know any alternatives.
@6r1d 6r1d added tidying up removing ambiguity, finding better solutions, documenting it all and adding tests enhancement New feature or request and removed enhancement New feature or request labels Mar 3, 2021
@6r1d
Copy link
Owner Author

6r1d commented Mar 18, 2021

I've read ALSA's seq API and other sources, so now I'm sure there's no "perfect way" to unify queue errors with "normal errors".
At some point later, I might make a "common queue" mechanism to unify input thread errors with errors returned by current API functions, but it feels like a premature optimisation currently.

@6r1d 6r1d closed this as completed Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tidying up removing ambiguity, finding better solutions, documenting it all and adding tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@6r1d