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

Stop using monolithic Error enum and use error types specific to each part of the API #48

Open
mitchmindtree opened this issue Nov 21, 2016 · 0 comments

Comments

@mitchmindtree
Copy link
Member

Although convenient for us, the biggest problem with using the same Error type everywhere is that rather than only representing the possible errors that may occur for each particular part of the API, it enumerates all errors, making it difficult for the user to determine what errors might actually occur when using certain parts of the API. Each method/function should have it's own error type which only enumerates the actual possible errors. This will be tricky as the coreaudio documentation rarely enumerates the possible errors that might actually occur, and in most places just returns a generic error code.

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

No branches or pull requests

1 participant