Unable to Index into AxisKeys from Inside Package about axiskeys.jl HOT 3 CLOSED

This is the downside of the "round brackets do lookup, square brackets do indexing" scheme -- because this is parsed as function definition, not a kind of setindex!, and can't be overloaded.

Some possible but not so pretty workarounds are:

tbl(:Estimate, :loo, :) .= mean(pointwise_ev)  # make a view
tbl[Key(:Estimate), Key(:loo)] = mean(pointwise_ev)  # use setindex!

from axiskeys.jl.

This is the downside of the "round brackets do lookup, square brackets do indexing" scheme -- because this is parsed as function definition, not a kind of setindex!, and can't be overloaded.

Some possible but not so pretty workarounds are:

tbl(:Estimate, :loo, :) .= mean(pointwise_ev)  # make a view
tbl[Key(:Estimate), Key(:loo)] = mean(pointwise_ev)  # use setindex!

Is there another way to do lookups? Worth noting that the first suggestion didn't work -- I still got the same error about methods. If this is a frequent problem, maybe this should be a macro so we don't get collisions like this?

from axiskeys.jl.

Oh, it's backwards, the order needs to match the definition. But that gives a different error:

julia> tbl(:Estimate, :loo, :) .= 0
ERROR: ArgumentError: could not find key :Estimate in vector [:loo, :p_loo, :loo_ic]

julia> tbl(:loo, :Estimate, :) .= 99  # note the .=
0-dimensional view(::Matrix{Float64}, 1, 1) with eltype Float64:
99.0

I agree it's a bit awkward, but I'm not so sure a macro is going to make this simpler. It could simply guess whether to index or lookup, and for Symbols this is not very confusing -- this is the line taken by other packages, but this one is a bit of an experiment to see if you can keep them more separate.

from axiskeys.jl.