Sheehan Olver
Sheehan Olver
I would take the lack of breaking changes as the _definition_ of stability. I don't think "v1.0" means the finished product, and if there are major issues there can always...
I don’t think it’s strange at all if v2 is the next release after v1, according to the principles of semantic versioning. there will almost always be breaking changes in...
I would say the criteria is that the interface is unstable in the short term. I.e. if v2.0 will be released within weeks or a month. But if v1.0 is...
Yes I understand. Just feel like some packages end up in v0.x forever because people have an illogical fear of v2.0... probably in part because Julia will probably never do...
Actually.... downstream I only ever use `conv`. What would you say to moving that out to its own package (Convolutions.jl) for v1?
JuliaDSP organisation?
Maybe JuliaMath makes more sense
The Toeplitz Hankel transforms are not very memory friendly due to a foolish decision on my part to transform a tensor all at once If we rewrite them to reuse...
I just gave you write access
I agree with @hyrodium: trying to keep performance high on _every_ supported version of Julia is going to add a lot of burden to both the code writer and maintainers....