Update Project.toml

[kshyatt]

Bump patch version for JLArrays stuff

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lkdvos]

Since we are now actually spending time updating these packages, it might actually pay off to merge StridedViews and Strided.jl

[kshyatt]

Since we are now actually spending time updating these packages, it might actually pay off to merge StridedViews and Strided.jl

Agreed, we should discuss which one should absorb the other at some point...

[Jutho]

There used to be only Strided.jl, and we have split off StridedViews.jl at some point to be used as a light-weight dependency. However, is there any path of merging these again that is not breaking. If Strided.jl absorbs StridedViews.jl, it will loose a StridedViews entry in its deps and compat section of the Project.toml. So StridedViews.jl can can remain installed. What then happens of people load both packages? Both packages export a StridedView name. However, the Strided.jl implementation only works for Strided.StridedView objects. I assume this rapid development cycle for StridedViews.jl will slow down sometime soon?

[lkdvos]

I have been thinking about this for a bit and I don't think I really see a way to do this in a non-breaking manner. I don't think I mind this breaking change all that much, I think having the two packages separate in the long run is a bit weird (especially now that package extensions exist)