Fix method ambiguities introduced by DataStructures.jl (when combined with Setfield.jl) #511
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.
(This PR is more like an issue report but I wanted to attach a possible solution. I am open to alternative fixes if any.)
It seems that the combination of
DataStructures
andSetfield
introduces some method ambiguities toBase.get
. They are betweenget(::DictType_from_DataStructures.jl, ...)
andget(obj, ::Setfield.Lens)
. I'm posting the issue here because I think it's easier to fix in DataStructures.jl. (cc @jw3126)You can invoke the ambiguity by, for example
I think the problem is that the
@delegate
macro declares the ownership of too many method signatures. It can be fixed by only delegating the 3-argget
method. In this PR, I propose to do this by adding a mapping between the method name and the desired arity like thisDataStructures.jl/src/delegate.jl
Lines 12 to 15 in 3f5c280
It's not the most elegant solution but it works and extensible (i.e., supporting a new method can be done by just adding a new entry to
_arities
).