-
Notifications
You must be signed in to change notification settings - Fork 4k
Description
Currently we have a mixture of base::stop() and rlang::abort() in the codebase. Should we make a deliberate choice to use one or the other?
If we decided to switch to {}rlang{}, we could:
-
change the codebase as we go along, switching from
basefunctions ({}stop(), warning(), message(){} to theirrlangequivalentsabort(), warn(), inform() -
make an addendum to
STYLE.mdon condition handlingWe could cover additional aspects of condition handling such as the wording of messages - for example, by using key words such as must or {}should{}.
Please discuss direction and why. :)
Note: the
arrowR package already depends onrlangso any outcome will not result in additional dependencies.Update: given @paleolimbot's suggestion of the
abort(glue))pattern I think we should include in scope adding a dependency on and using{}glue{}.
Reporter: Dragoș Moldovan-Grünfeld / @dragosmg
Related issues:
- [R] More special handling for known errors in arrow_eval (is related to)
Note: This issue was originally created as ARROW-15359. Please see the migration documentation for further details.