Skip to content

Commit 9df3a6b

Browse files
committed
Updated NEWS and README for new axis behavior.
1 parent 291ffd7 commit 9df3a6b

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed

NEWS.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,35 @@
11
# ComponentArrays.jl NEWS
22
Notes on new features (minor releases). For more details on bugfixes and non-feature-adding changes (patch releases), check out the [releases page](https://github.com/jonniedie/ComponentArrays.jl/releases).
33

4+
5+
### v0.11.0
6+
- Calling `axes` on a `ComponentArray` returns a new `CombinedAxis` type!
7+
- Doing things The Right Way™!
8+
- No more complicated and error-prone custom broadcasting machinery!
9+
- No more wierd special cases!
10+
### v0.10.0
11+
- All indexing now slices rather than sometimes viewing and sometimes slicing!
12+
- Property access methods (i.e. "dot-access") still use views!
13+
```julia
14+
julia> x = ComponentArray(a=1, b=[4,2])
15+
ComponentVector{Int64}(a = 1, b = [4, 2])
16+
17+
julia> x.b # Dot-access still views by default
18+
2-element view(::Vector{Int64}, 2:3) with eltype Int64:
19+
4
20+
2
21+
22+
julia> x[:b] # Slicing now slices
23+
2-element Vector{Int64}:
24+
4
25+
2
26+
27+
julia> @view x[:b] # Use @view to view
28+
2-element view(::Vector{Int64}, 2:3) with eltype Int64:
29+
4
30+
2
31+
```
32+
433
### v0.9.0
534
- Construct `ComponentArray`s from `Dict`s!
635
```julia

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ in [DifferentialEquations.jl](https://github.com/SciML/DifferentialEquations.jl)
2727
[Optim.jl](https://github.com/JuliaNLSolvers/Optim.jl), but anything that requires
2828
flat vectors is fair game.
2929

30+
Check out the [NEWS](https://github.com/jonniedie/ComponentArrays.jl/blob/master/NEWS.md) for new features by minor release version.
31+
3032

3133
## General use
3234
The easiest way to construct 1-dimensional ```ComponentArray```s (aliased as `ComponentVector`) is as if they were ```NamedTuple```s. In fact, a good way to think about them is as arbitrarily nested, mutable ```NamedTuple```s that can be passed through a solver.

0 commit comments

Comments
 (0)