Alexander Plavin

Julia 1.8.3 indeed fixes that bug, and all tests now pass with no changes from my side. Anything else I need to modify in this PR?

Bump @mcabbott This PR makes `AxisKeys` work with 1.9 and be consistent with that version. Would be great to merge soon, given that 1.9 doesn't seem that far away. Further...

Another bump... @mcabbott

Broadcasting is now supported (`Accessors#master`, to be released soon)! All examples from the first post work on `Vector`s. The remaining `SVector` issues are because of their `setindex` method that leads...

I think this PR is useful and wouldn't have consistency issues if defined with some restrictions. I actually tried recently `@modify(f, dct.vals |> Elements())` hoping that it would work out...

`values()` is not the same as `vals`. `vals` is a dense array larger than the actual `length(dict)`. Some of its elements are actual dict values, others are uninitialized. So, potential...

Regarding Accessors, I've also wondered whether `@modify(f, dict |> values |> Elements())` can be implemented as basically `dict.vals = map(f, dict.vals)` (plus some checks). Doesn't look directly possible, because both...

> starting from the type Pair and the columns [1, 2, 3], ["a", "b", 2], I would like to figure out that the eltype for the resulting StructArray (which should...

I personally don't have anything against generated functions here. Originally, this switch from generated to regular functions was introduced in a bugfix https://github.com/JuliaObjects/ConstructionBase.jl/pull/60. I guess, whenever fields == properties, one...

It is widely used in interferometry (of course). I have `mas` in my package locally, and find myself using it pretty often. And I'm quite sure the abbreviation doesn't conflict...