No method matching `dirname(::Nothing)`

[theogf]

Pre-submission checklist

• I have searched existing issues and confirmed this is not a duplicate.

Client

Neovim

Julia versioninfo()

1.12

JETLS version

2024-04-06

Reproduction with the VSCode reference client

• I have confirmed this issue also reproduces with the VSCode reference client.
• This issue does NOT reproduce with the VSCode reference client, but I believe JETLS-side changes are needed.

Description

I have a bunch of submodules that start with:

include(joinpath(dirname(pathof(parentmodule(@__MODULE__))), "docstrings.jl"))

This create an error diagnostic with

MethodError: no method matching dirname(::Nothing)
   │ │ │      The function `dirname` exists, but no method is defined for this combination of argument types.
   │ │ │      
   │ │ │      Closest candidates are:
   │ │ │        dirname(!Matched::FilePathsBase.AbstractPath)
   │ │ │         @ FilePathsBase ~/.julia/packages/FilePathsBase/NV2We/src/aliases.jl:11
   │ │ │        dirname(!Matched::AbstractString)
   │ │ │         @ Base path.jl:183 JETLS/save (toplevel/error) [3, 1]

Steps to reproduce

Create a submodule with the line above, run the jetls diagnostics on it.

JETLS configuration (if applicable)

No response

Additional context (optional)

No response

[ufechner7]

Workaround: use @__DIR__ instead.

The warning is correct:

julia> typeof(pathof(@__MODULE__))
Nothing

pathof(@__MODULE__) can be nothing. JETLS cannot prove that it cannot be nothing in your code.

[joa-quim]

I get the same error in a line that has joinpath(dirname(pathof(GMT)), where

typeof(pathof(GMT))
String

[theogf]

pathof(@MODULE) can be nothing. JETLS cannot prove that it cannot be nothing in your code.

Can it really be nothing if it is in module ... end scope?

[giordano]

pathof(@MODULE) can be nothing. JETLS cannot prove that it cannot be nothing in your code.

Can it really be nothing if it is in module ... end scope?

Yes

Return the path of the m.jl file that was used to import module m, or nothing if m was not imported from a package.

The fact you're inside a module doesn't say anything about the import mechanism, that's completely orthogonal.