Checking Benchmark CI in my local repo for [Drop support for versions of Julia lower than v1.6] #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Fredrik Ekre <[email protected]>
Added check option to cholesky
* fix for issue JuliaArrays#894 * bump version
spelling mistake
Update initializers.jl
* Make scalar multiplication type stable Also provide a unary + operator. * Add tests for inferring linear algebra * We cannot infer for Julia 1.1 * Add more @inferred tests * New version 1.1.2
* Add zero(::Type{<:SDiagonal})
* version bump to v1.1.3
…Arrays#908) * views of SArray use indexing * move fn defn to abstractarray.jl * wrap elements in Scalar * restrict index types * allow indexing with SArrays * views for CartesianIndex, inferred in tests * bump version to v1.2.0
* Reverse for SArray and MArray * fix test on older julia versions * define reverse for StaticArrays * version bump to v1.2.1
* reshape with Val * check type inference * Require at least one SOneTo in rdims Co-authored-by: Mateusz Baran <[email protected]> * version bump to v1.2.2 Co-authored-by: Mateusz Baran <[email protected]>
* broadcasting for Diagonal StaticArrays * Add tests for SizedArrays * add tests for inplace broadcasting * version bump to v1.2.3
* Fix JuliaArrays#920 * if needs to be static * bump version
* Run CI on latest released 1.x version * fix broken tests on v1.6+ * disable `svd` kwarg const-prop test on v1.6 and later * mark `svd` test as broken on v1.6 and later & swap between `@test` and `@test_broken` for `abstractarray.jl` tests
…ties for `lu` (JuliaArrays#932) * fix `qr` method ambiguities (JuliaArrays#931) and lingering `lu` ambiguities (JuliaArrays#920) * fix inferrence issues due to using `@invoke` for `lu` keyword arguments * bump version
* Fix reshaping of a mutable StaticArray * more reshape changes
* Add a two-argument show method for SUnitRange. * bump version to 1.2.7 Co-authored-by: Mateusz Baran <[email protected]>
Fix typo
Update util.jl
* various fixes to `norm` & more tests * fix test failure; widen signatures * restrict type-stability tests to v1.2+ * fixes/improvements from code-review * address remaining issue for `_inner_eltype` of empty arrays * use `_inner_eltype(x)` for `_norm_p0` and adjust signature to `AbstractArray` - also fix copying errors from last commit * bump patch version
* permutedims, easy cases * fix * add sizedarray methods * tests * bump version
* specialize muladd * bump version
…ixes JuliaArrays#887) (JuliaArrays#945) * Expand signature of `normalize` from `StaticVector` to `StaticArray` (fixes JuliaArrays#887) * Bump patch version
These improve inferrence to guard against very minor invalidations from packages that extend `==`.
In preparation for JuliaLang/julia#41885
* Add type-assertion to length * Add assertion to method with types * Add tests
* Fix issue JuliaArrays#961 * only test on newer Julia versions * bump version
implement `float` and `real` for `StaticArray` (fix JuliaArrays#935)
…rays#980) Having access with v.x etc makes the *concrete* SVector interface much more usable for geometry; indeed, it will "just work like you expect" without the need to resort to a custom FieldVector type. This makes the concrete SVector/MVector interface fatter, but I don't think it can do any harm to people who don't want to use it.
* note named access for SVector in FieldVector docs * Update api.md
…uliaArrays#982) * Make `vec` just return the argument for `MVector` and `SizedVector`. * bump version
- I actually don't understand this one: it was previously bounded to _below_ v1.5 - but that would indicate we assume allocations on later versions?
* Force more inlining in `reduce` * bump version
* specialize mul_fast and add_fast to allow FMA * bump patch version number
- require unchanged ambiguity counts or an updated value of `allowable_ambiguities`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.