-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add fatal_error()
to the language
#1402
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1402 +/- ##
==========================================
- Coverage 89.88% 89.87% -0.02%
==========================================
Files 63 63
Lines 10513 10525 +12
==========================================
+ Hits 9450 9459 +9
- Misses 1063 1066 +3
|
I prefer |
Good point. |
exit()
to the languagefatal_error()
to the language
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, a couple of optional suggestions.
Closes #1393 .
Note that there is no way to parse this and also allow variables named
exit
, so this would immediately reserve the keyword. Based on a github search, I found only one package which usesexit
as a variable name. If this is a serious concern we could consider different names likestop
or something likefatal_error
which is almost certainly unused.Submission Checklist
Release notes
Added
fatal_error()
, which is similar toreject()
but rather than signaling an error which is recoverable, signals an error which should terminate execution immediately.fatal_error
is now a reserved word.Copyright and Licensing
By submitting this pull request, the copyright holder is agreeing to
license the submitted work under the BSD 3-clause license (https://opensource.org/licenses/BSD-3-Clause)