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

Use More Descriptive Errors than Nothing #1630

Closed
2 tasks
iamrecursion opened this issue Mar 29, 2021 · 0 comments · Fixed by #1734
Closed
2 tasks

Use More Descriptive Errors than Nothing #1630

iamrecursion opened this issue Mar 29, 2021 · 0 comments · Fixed by #1734
Assignees
Labels
--breaking Important: a change that will break a public API or user-facing behaviour p-highest Should be completed ASAP

Comments

@iamrecursion
Copy link
Contributor

Summary

There are multiple parts of our API that use Nothing as a dataflow error. This isn't descriptive in the IDE, so we want to replace these with more descriptive types.

Value

Better UX.

Specification

  • Do the thing.

Acceptance Criteria & Test Cases

  • The thing is done.
@iamrecursion iamrecursion self-assigned this Mar 29, 2021
@iamrecursion iamrecursion added Category: Stdlib --breaking Important: a change that will break a public API or user-facing behaviour p-highest Should be completed ASAP labels Mar 29, 2021
@iamrecursion iamrecursion added this to the Alpha 4 milestone Mar 30, 2021
@iamrecursion iamrecursion modified the milestones: Alpha 4, NCBIR Apr 26, 2021
@iamrecursion iamrecursion mentioned this issue May 10, 2021
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--breaking Important: a change that will break a public API or user-facing behaviour p-highest Should be completed ASAP
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant