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

represent the error info with singleton types instead of NamedTuple #11

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

nsajko
Copy link
Collaborator

@nsajko nsajko commented Jan 17, 2025

I think this is a bit nicer to understand and use. The information is slightly less granular, as there's no distinction any more between:

  • the input contains negative values
  • the input contains typemax(T)
  • the input contains both of the above

That should be OK though, given that the information is supposed to serve simply for choosing a good error message.

I think this is a bit nicer to understand and use. The information is
slightly less granular, as there's no distinction any more between:
* the input contains negative values
* the input contains `typemax(T)`
* the input contains both of the above

That should be OK though, given that the information is supposed to
serve simply for choosing a good error message.
@nsajko nsajko merged commit 3048b89 into JuliaArrays:main Jan 17, 2025
14 checks passed
@nsajko nsajko deleted the singleton_type_error_status branch January 17, 2025 13:56
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

Successfully merging this pull request may close these issues.

1 participant