Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make LSP features work even if we can't find a module #52

Open
certik opened this issue Dec 24, 2024 · 0 comments
Open

Make LSP features work even if we can't find a module #52

certik opened this issue Dec 24, 2024 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@certik
Copy link
Contributor

certik commented Dec 24, 2024

When opening a file (module or a program) that imports other modules but we can't find their .mod files, here is how it should behave:

  • LFortran will still construct ASR on a best-effort basis (by guessing and skipping stuff as needed)
  • It will report errors "module X not found" for each use X statement
  • VSCode will put red squiggles over each such use X, so the user will know that we can't find the .mod files
  • But all LSP features will still work, based on the best-effort ASR that LFortran internally creates; for example VSCode will still show all document symbols
@certik certik added bug Something isn't working enhancement New feature or request labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant