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
tildes in quosures #924
Comments
It's a conjunction of multiple issues.
Ideally quosures would be a native data type in R with special deparsing behaviour, and then quosures would behave as you'd expect in all aspects. |
Makes sense. I'll give the patch a shot as that seems like a very small change that doesn't require me internalizing much of the code base. If I can get the tests to pass I'll submit it. Later this week likely. |
I now have three packages failing CRAN due to stringsAsFactors, so I need to address that first. So might be another week or so. |
No worries! There's no hurry. |
This seems odd to me (rlang 0.4.4).
Two unexpected things:
My mental model of how this all works is incomplete, but I feel it should be possible fetch the correct tilde to evaluate in
base_tilde_eval
withfindVar
(in function finding mode anyway, if it does such thing likeget
does), instead of just going directly to the primitive. Obviously a pretty unlikely corner case to hit (if indeed I'm even correct about this being an error).Not sure what's going on with the environment. Feels like
quo_env
should be the global environment here? Or is that still some kind of mask env even without data?The text was updated successfully, but these errors were encountered: