Changes added to Modern Fortran 2 cause the following behaviour when used in combination with the fortran-language-server extension for VS code.

It's worth mentioning that it looks awfully similar to this bug reported in the fortran-language-server extension for VS code.