Orson Peters
Orson Peters
It is unfortunate that `np.view` doesn't document what kind of views are 'allowed' and which would be undefined behavior. Then again, `np.empty` is essentially instant undefined behavior anywhere so there's...
@ngoldbaum The `view` isn't called from Rust code, that happens in Python. The Rust code just gets an `ndarray` and has no idea if it's in a valid state or...
You're using the 32-bit runtime. Install `polars[rt64]` if you want to process more than 2^32 rows.
The backtrace indicates it's a rustc bug.
@mcrumiller There's already a lot more context in the linked rust-lang issue.
I'm not sure if we want false strictness. Won't this also allow other silly things such as returning strings when the return type is set to `pl.Int64`?
Do you still have the same problem if you edit `rust-toolchain.toml` to a more recent Rust nightly version?
I just don't understand why we get `memory allocation of 648518346341351440 bytes failed`. Is this a rustc issue?
I literally just removed all the code that special-cases all this stuff because it all wasn't being updated and was buggy :( Can we not make the generic path faster...
> Not sure how I'm supposed to know that code I can't see used to be there 🤷 You're not, I'm not blaming you :)