You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've stumbled upon some strange behavior today when comparing rio with the builtin load/save. I presume the first part where the object is not imported in the global environment is intentional. Is the second part related?
rio::export(iris, "test.RData")
save(iris, file="test2.RData")
rio::import("test.RData") # doesn't actually import iris
load("test2.RData") # imports iris
rm(iris)
load("test.RData") # is named x
load("test2.RData") # is named iris
The text was updated successfully, but these errors were encountered:
@hliebert Thank you for reporting this. This behavior is intentional because rio::import() should (always) return a data frame. Rather than the side-effect of putting sometime to the current global environment.
The intended way to use rio::import() for .RData is like this (not very different from .RDS):
I've stumbled upon some strange behavior today when comparing rio with the builtin load/save. I presume the first part where the object is not imported in the global environment is intentional. Is the second part related?
The text was updated successfully, but these errors were encountered: