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

Ensure error handling in CoreGraphics and attendant frameworks happens at API boundaries #1323

Closed
DHowett-MSFT opened this issue Nov 4, 2016 · 1 comment

Comments

@DHowett-MSFT
Copy link

  • All internal methods should be able to report failure without aborting, whether through an HRESULT return or a nullptr return.
  • All external API surface methods should be able to fail where possible.
    • Some frameworks do not provide for errors to be returned. The reference platform has been observed calling abort().
    • If there is an opportunity for a failure return, it should be taken. API functions that can return newly-created resources are safe to return nothing and emit a trace error.
@rajsesh
Copy link
Contributor

rajsesh commented Nov 18, 2016

We have normalized the design on this, so we can close this now.

@rajsesh rajsesh closed this as completed Nov 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants