ComponentArrays vs LabelledArrays

[amrods]

I’ve been a user of ComponentArrays.jl for a while. Just recently discovered LabelledArrays.jl. They strike as very similar. Are there any fundamental differences between them?

Just as example, this is the kind of use for which I employ ComponentArrays:

Parsimonious way to unpack big structs

using your example, it would be using ComponentArrays using UnPack p = ComponentArray(α=0.1, β=0.2, γ=0.3) function f2(x; p=p) @unpack α, β, γ = p return x^(α) + x^(β) + x^(γ) end I also like to organize the parameters inside the ComponentArray, for example: using ComponentArrays using UnPack # full model function model(p; data=data) @unpack p1, p2 = p @unpack data1, data2 = data # component 1 r1 = f1(p1; data=data1) # component 2 r2 = f2(p2; data=data…

Are there any advantages of LabelledArrays over ComponentArrays in that case?

[ChrisRackauckas]

ComponentArrays.jl is probably just better at this point.

[nrontsis]

Sorry for the necropost, but would you say that this is still the case?

I found ComponentArrays.jl to be a really cool package, but after using it for a couple of days I run into a couple of issues that made me appreciate the subtleties of the package. I am opening PRs to address some of these, but I think it would be great if the two packages were to merge to one, so that we don’t write code and fix bugs twice

What do you think?

[ChrisRackauckas]

Things are pretty much just going to ComponentArrays.jl at this point. There’s no reason to kill LabelledArrays.jl, it does what it does, but ComponentArrays.jl has a much bigger feature-set so we advocate its use in the docs.

[nrontsis]

@ChrisRackauckas

There’s no reason to kill LabelledArrays.jl

Perhaps I am missing context here, but I assume that keeping LabelledArrays.jl has a maintenance cost? Over 2022, there were almost twice as many commits to LabelledArrays.jl as compared to ComponentArrays.jl.

My point is that if the efforts to maintain LabelledArrays.jl were instead channeled to ComponentArrays.jl then we could end up with a more robust package.

I am somewhat biased here because I ended up opening 3 issues and 4 PRs after a few days of interacting with ComponentArrays.jl.

[ChrisRackauckas]

@nrontsis

Over 2022, there were almost twice as many commits to LabelledArrays.jl as compared to ComponentArrays.jl .

My point is that if the efforts to maintain LabelledArrays.jl were instead channeled to ComponentArrays.jl then we could end up with a more robust package.

The amount of work into LabelledArrays.jl has been effectively zero. It’s straightforward to maintain and takes no time.