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

In abort() etc, should call be an integer? #30

Closed
hadley opened this issue Feb 14, 2017 · 1 comment
Closed

In abort() etc, should call be an integer? #30

hadley opened this issue Feb 14, 2017 · 1 comment

Comments

@hadley
Copy link
Member

@hadley hadley commented Feb 14, 2017

Sometimes when signalling an error, it's useful to use the call one level up the stack (i.e. in check() style functions). Maybe as well as being an logical, call() could also be an integer with the same interpretation as in call_stack() etc?

@lionel-
Copy link
Member

@lionel- lionel- commented Feb 14, 2017

that's a really good idea, it would also be helpful for the warnings in the lazyeval dots checking function.

lionel- added a commit to lionel-/rlang that referenced this issue May 23, 2017
@lionel- lionel- closed this in #152 May 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants