You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hover over functions can produce vastly different results depending on how the function is written.
Hover results will be different depending on whether the function type and the function result are present.
The output should be standardised regardless of how the function is written.
! simple functionfunctionfun1(arg)
integer, intent(in) :: arg
integer:: fun1
endfunction fun1! function with type on definition, implied resultintegerfunctionfun2(arg)
integer, intent(in) :: arg
endfunction fun2! function with returnfunctionfun3(arg) result(retval)
integer, intent(in) :: arg
integer:: retval
endfunction fun3! function with type on definition and returnintegerfunctionfun4(arg) result(retval)
integer, intent(in) :: arg
endfunction fun4
The text was updated successfully, but these errors were encountered:
Functions now all display the same signature:
`type` `keywords` `function` `name(args)` `result(val)`
- Submodule module procedure functions now display like so
- functions without an explicit type or result now display like so
- Nested functions i.e. using functions as args displays like so
Closes Add support for Fortran scope/block snippets #47
Adds a series of hover unittests.
Also renamed the result variables
Hover over functions can produce vastly different results depending on how the function is written.
Hover results will be different depending on whether the function type and the function result are present.
The output should be standardised regardless of how the function is written.
The text was updated successfully, but these errors were encountered: