Module inlining a public routine results in uncompilable code if there is a wildcard import.

[arporter]

If we have a module that does use my_mod and contains a routine that calls my_sub and then we "module inline" my_sub into that module then we get un-compilable code:

module my_mod
    public
contains
    subroutine my_sub
    end subroutine my_sub
end module my_mod

and

module caller_mod
  use my_mod
contains
  subroutine other_sub
    call my_sub()
  end subroutine
end module caller_mod

This is because the compiler then has two routines named my_sub in scope.

We can spot this situation by checking for a 'wildcard' import from the module containing the routine being inlined.
We could potentially solve it by adding a renaming to the import of the original routine symbol.

[arporter]

USE B, T1 => C

[arporter]

Unfortunately, even the PSyIR fparser2 frontend doesn't support this form :-(