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

[Design] Error model #2

Open
mratsim opened this issue Oct 20, 2018 · 0 comments
Open

[Design] Error model #2

mratsim opened this issue Oct 20, 2018 · 0 comments
Labels

Comments

@mratsim
Copy link
Owner

mratsim commented Oct 20, 2018

Error model is still to be decided.

Currently asserts are used https://github.com/numforge/laser/blob/be3326bca5d9096e912530c6ed946bb89ee01b6f/laser/strided_iteration/map_foreach.nim#L106-L110

Literature:

Challenges:

  • should the interface exposed be left to higher-level lib? (i.e. leave only asserts as those are removed on release builds)
  • If not:
    • Distinguish between recoverable and unrecoverable errors (bugs).
    • For embedded devices recoverable errors "API" must be documented, whether error code or exceptions are chosen.
  • Macros like forEach cannot use error codes, high level wrapper should take care of that
@mratsim mratsim added the RFC label Oct 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant