julia-vscode
Possible method call error for re-exported function
The "possible method call error" linting seems to have some difficulties at the moment, but it's not always quick or easy to come up with a MWE. Here's one case where I think I know the source of the problem:
In this case, categorical is simply re-exported from MLJ, so I think that's where the difficulty is. (I don't have any explicit using CategoricalArrays in my project...)
Thanks, that's really helpful (the clue to the issue is the 0 methods for function.. in the hover - we've found the symbol for the function but not the associated methods). I'll have look
I seem to be getting this while using Plots:
although the plot() works just fine. I'm guessing it's the same problem?
I'm getting it too with several packages, assuming it's a same problem.
Also, it happens to be for perfectly working code when I'm trying to parse JSON from external process:
Getting this when calling my own functions, the issue seems to be keyword args:
I was under the impression that keyword arguments were required to have a default value. Has that changed recently or was that never the case?
@pfitzseb Was this issue closed by accident? It seems like all the above-mentioned issues are still present (except the one related to missing default values).
If this issue was closed on purpose, it should definitely be re-opened. Referring to a comment I made a few days ago for a 0 method error with the plot and plot! commands from Plots.jl, the issue exists still/again. My point on the Plots.jl repo was that the 0 method error ONLY occurs on the plot and plot! commands and not on any other function/method whether re-exported nor whether those functions/methods included keywords arguments.
Referring to the same comment I had shared before, it seems as though moving to Julia v1.10.0 has resolved the 0 method error I was seeing because of the new language parser: JuliaSyntax.jl.