gnikit

Hi @gbogopolsky good catch. This is indeed a bug. As you can tell I don't tend to work with `type is` select constructs and hence this fell through the cracks....

So I had a look, the error you are getting from pytest is because of the unittest breaks if you remove lines 23-26 if you have a look at the...

Okay I had a look and it seems okay to me. You can see that the single `type is` is actually tested in the same file, lines 26-32. If you...

So I do think that the error is from `fortls` but I am unable to replicate myself. Here is my screenshot  The diagnostic error at `this%a` is from the...

1. Your `fortls` settings look good to me. If you want to autoinclde PP definitions (or at least allow `fortls` to try you have to specify `include_dirs` e.g. `"include_dirs": ["include"],`...

And just to check, you are using fortls v 2.2.5?

> Same behavior is observed on Windows with `fortls` v.2.5.5 through `conda-forge` To be honest, I wouldn't expect conda-forge to be any different. ~~As a last attempt could you copy-paste...

Yeah preprocessor definitions are a bit flimsy because they are implemented as string substitutions. That means that every instance of the word `IS` is replaced with `type(tis)`. That is why...

That sounds like an edge case I missed. `EXTERNAL`s where the keywords are not defined along with the declaration of the fun/sub are implemented in a very unintuitive manner so...

I think you mean this, `got to implementation` will just say that there is no implementation, while it should be jumping to `fun1` ```fortran program main external sub1 ! external...