deprecate error(::Exception) and error(::Type{Exception}) #9690
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Great! |
ivarne
added
the
domain:error handling
jakebolewski
force-pushed
the
jcb/deperr
branch
from
0a2dc10
to
3587a1f
Compare
|
👍 ! |
jakebolewski
force-pushed
the
jcb/deperr
branch
from
3587a1f
to
f2942a0
Compare
jakebolewski
added a commit
that referenced
this pull request
Jan 11, 2015
deprecate error(::Exception) and error(::Type{Exception})
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are redundant and currently just defer to throw. I feel we want move away from generic
error()messages where possible, so we should encourage people to throw more specific Exception types.cc @ivarne