-
Notifications
You must be signed in to change notification settings - Fork 3
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
BUG: walkAST() may give Error: Cannot walk expression. Unknown object type 'list' #27
Comments
Another problematic type is > y <- future::future_lapply(1L, function(a, b) typeof(b), b = expression())
Error: Cannot walk expression. Unknown object type 'expression' |
HenrikBengtsson
added a commit
that referenced
this issue
Jun 29, 2017
…wn object type 'list'" and same for 'expression' (Issue #27)
HenrikBengtsson
added a commit
that referenced
this issue
Jun 29, 2017
HenrikBengtsson
added a commit
that referenced
this issue
Jun 29, 2017
…ning" will cause walkAST() to only produce a warning (instead of an error) if there is "unknown type" is detected. This allows users to (try to) keep working in case there a data type is discovered that was not accounted for (Issue #27).
This should have now been fixed in the remotes::install_github("HenrikBengtsson/globals@develop") I've added package unit tests for it. I'm currently running reverse-dependency package tests (for everything on CRAN and Bioconductor), which will take some time. I'll reopen if I find something unexpected. |
HenrikBengtsson
added a commit
that referenced
this issue
Jun 30, 2017
HenrikBengtsson
added a commit
that referenced
this issue
Jul 1, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In futureverse/future#156, it was reported that:
with traceback:
In the above call,
expr
is effectivelyand walking the AST on that expression gives the error:
The error is triggered on the second component of
expr
, which is of typelist
:Note, this is not the same as:
because there we have:
The current
walkAST()
code assumes the latter, but not the former./cc @ck37
The text was updated successfully, but these errors were encountered: