Conversation
neopolarspolars 1.0.0
|
Thanks for working on this. Some thoughts:
|
Thanks, but that doesn't simplify much IMO.
This was deprecated one year ago, which is why it wasn't implemented in the rewrite. The deprecation message recommended using head + collect, hence my implementation: https://github.com/pola-rs/polars/pull/17278/files#diff-6f7ee6a0f7f99cb158f4d68d883a118b9fab6175602e8696739d900c8b0d864f |
There are several additional arguments that are passed to.
If so, why is it not marked as deprecated? |
It was an oversight on my side, I thought this was part of the functions exported by |
|
@eitsupi currently
The problem with this approach is that wrong arguments would be undetected since library(polars)
library(tibble)
pl$LazyFrame(x = 1) |> as_tibble(foo = 2)
#> # A tibble: 1 × 1
#> x
#> <dbl>
#> 1 1Should we add a check like that on Edit: in the meantime, I've manually added the arguments and point to |
|
@etiennebacher In my opinion, S3 methods should simply ignore empty dots. Otherwise, it becomes difficult to write common processes for different classes. As I wrote before, consider making |
|
I get an error with
Not sure this works with functions accessed via In any case, I want to keep the dots check in Thanks for your help! I think this is ready for 1.0.0 now. |
|
Sorry, I didn't understand the inheritance of arguments well. |
|
Blocked by pola-rs/r-polars#1439, there's a substantial performance decrease on one of my test data (from 10s to 48s). |
Can such a large slowdown be explained by |
|
I see, I don't think this is a blocker anyway (it's caused by something already released upstream and there's nothing we can do about it here) |
|
Right, I can merge this now that the installation of polars from r-multiverse points to 1.0.0 |


No description provided.