-
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
walkAST()
gives error with S7 object.
#93
Milestone
Comments
egenn
changed the title
BUG:
Jan 22, 2025
walkAST()
gives error with S7 object.walkAST()
gives error with S7 object.
Thanks. I think a minimal reproducible example of this is: A <- S7::new_class(name = "A")
obj <- A()
globals::walkAST(obj, call = identity)
#> Error: Cannot walk expression. Unknown object type 'object' |
I actually found a smaller example: obj <- S7::S7_object()
globals::walkAST(obj, call = identity)
#> Error: Cannot walk expression. Unknown object type 'object' |
|
Got a minimal reproducible example that doesn't bring in non-base-R packages thanks to RConsortium/S7#524 (comment); > obj <- asS3(methods::getClass("S4")@prototype, complete = FALSE)
> globals::walkAST(obj)
Error: Cannot walk expression. Unknown object type 'object' Now I can add this as a unit test, and then fix it. |
HenrikBengtsson
added a commit
that referenced
this issue
Jan 23, 2025
HenrikBengtsson
added a commit
that referenced
this issue
Jan 23, 2025
This has been fixed in the next release, e.g. > globals::walkAST(S7::S7_object())
<S7_object> Until submitted to CRAN, it's available as: remotes::install_github("futureverse/globals", ref = "develop") Thanks for reporting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi - This is similar to #28, #27, but with S7 objects.
Passing an S7 object to a
future.apply::future_lapply()
call throws errorError: Cannot walk expression. Unknown object type ‘object’
.Runs with
future.globals = FALSE
.Create S7 object:
Minimal example:
Works with globals disabled:
The text was updated successfully, but these errors were encountered: