Open plevold opened 3 years ago
I notice the same on my side. Any idea about how to fix it?
@plevold Is the rest of the syntax for this example legal? Can I ignore the diagnostic and linting errors in :: my_func
and this
?
This has now been fixed in fortls
v1.14.4 . The autocomplete suggestions are not "working" as expected i.e. the suggestions will not be limited to what was included with import. That will be fixed in a future release see: https://github.com/gnikit/fortls/issues/8
@plevold Is the rest of the syntax for this example legal? Can I ignore the diagnostic and linting errors in
:: my_func
andthis
?
The original example was missing the declaration of the this
argument. Also strictly speaking the type should have been abstract since it has a deferred procedure. Here's an example that gfortran compiles with no complaints using -Wall
:
module class_myclass
implicit none
private
public myclass
type, abstract :: myclass
private
contains
procedure(my_func), deferred :: my_func
end type
interface
subroutine my_func(this)
! error happens when I start typing "myclass" here
import myclass
class(myclass), intent(in) :: this
end subroutine
end interface
end module
This has now been fixed in fortls v1.14.4 .
Awsome! Thanks a lot for the effort. This project is making Fortran development much more pleasant!
@plevold Thanks for the example code. I will try and sort out the autocomplete suggestions in the next few weeks.
Glad to see people using the new fortls
@gnikit : You just need to be quite deep inside the fortran github bubble to find out about it. I updated my small guide (https://github.com/JHenneberg/Guide_VSCode-fortran) with your extension.
With this minimal example:
I get the following tracebacks in the VSCode output view when I start typing "myclass" after "import":