Oliver Schulz
Oliver Schulz
Speaking as a user, I love the "table-ness"! :-)
> Speaking as a user, I love the "table-ness"! :-) I mean the fact that it implements the Tables.jl interface (SplitApplyCombine I haven't used much).
While it would, in theory, be nice to be able to grow an UnsafeVector, overwriting the parent array would be just a bit too unsafe ... :-) `pop!` and `popfirst!`...
Well, for the use case of sliding windows, you would just create many unsafe views, but they wouldn't be resized. And if you need to resize an unsafe view, you...
Actually, the `calloc`-trick presented by foobar_lv2 in a [recent thread on the Julia Discourse](https://discourse.julialang.org/t/resize-matrix/2379/25?u=oschulz) may profit from a kind of mutable unsafe vector that knows it's maximum bounds. It would...
Ok, I think a mutable version of `UnsafeArray` that would support use cases like we discussed on discourse (oversized malloc/calloc, growing via page faults and then handing final array to...
As for sliding window use cases, I believe the right approach is to simply create a lot of throw-away views, as @uviews make them very very cheap.
This could actually mesh well with [TemporaryArrays.jl](https://github.com/oschulz/TemporaryArrays.jl/tree/dev) (new package, still in design phase). The idea there is to provide reusable temporary arrays, to avoid allocation cost for temporary arrays (e.g....
Good point, let's keep this issue as a reminder.
Also relates to #8, e.g. for `square`/`sqrt`.