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

Figure out a strategy for handling common (usually ignored) errors #31

Open
brendanzab opened this issue Apr 8, 2018 · 0 comments
Open

Comments

@brendanzab
Copy link
Member

Here are some common errors that are often ignored, but would be nice to be able to avoid either statically or ensure they are accounted for at runtime:

  • Out of memory errors
  • Integer overflow/underflow (ranged integers?)
  • Divide by zero
  • Loss of numerical precision
  • Units of measure mismatches (compile time units of measure lib?)
  • Index out of bounds (track array/matrix dimensions at the type level?)
brendanzab added a commit that referenced this issue Jun 12, 2018
Rename conditional types to assertion types
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