Zachary P Christensen

Would be great if these could be fixed soon. I'm trying to ensure improvements are stable across Julia versions for #1596 and these errors make it pretty difficult.

This was driving me crazy so I worked on it (for an embarrassing amount of time b/c my lua skills are weak). ```lua local iron = require('iron') local view =...

I'm hopeful some of these can eventually be fully transitioned to a proper dependency in the appropriate downstream package. But I'm personally trying to make sure we get everything to...

Just chiming in to reassure that I will keep adding tests for code I've contributed to.

I think this https://github.com/JuliaLang/julia/issues/24909 nicely illustrates the problem I'd like to be able to solve. I guess the long term solution would be having something like a memory buffer type...

> I'm curious if that'd help LoopVectorization's compile time performance TBH, I hadn't given code gen a thought. However, `push!` loops certainly are a common pattern in code generating functions...

One of the biggest reasons I want this is b/c it would make it possible to have AxisIndices.jl to just provide per dimension traits to a memory buffer with something...

@chriselrod. Does the type info provide anymore information on how you generate code for vectorization beyond its size (a part from what `vload` needs to know for each element)? For...

I was just thinking of a linear set of elements. I'm trying to address this issue by creating something like `LinearIndices` or `CartesianIndices` but it actually communicates the transformations an...

@chriselrod correct me if I'm wrong here, but it seems like the path forward is to have ArrayInterface depend on [ManualMemory.jl](https://github.com/JuliaSIMD/ManualMemory.jl) (which I anticipate remaining a very light-weight dependency).