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

No diagnostic when completion fails because of a compiler error #689

Open
adpi2 opened this issue Jan 4, 2023 · 1 comment
Open

No diagnostic when completion fails because of a compiler error #689

adpi2 opened this issue Jan 4, 2023 · 1 comment

Comments

@adpi2
Copy link
Member

adpi2 commented Jan 4, 2023

Reproduction Step

  1. Create a new snippet
  2. Type this without "saving"
def foo(x1: Option[String]): Option[String] = ???

def foo(x2: String): String = ????

foo(1).

I don't get any auto-completion on foo(1)..

This is expected since foo(1). does not type-check but there is no clue explaining me why.

Expectation

It would be great if we could have some diagnostics explaining why the completion failed.

@julienrf
Copy link
Contributor

I agree that it would be good to have a way to signal to the user that the code did not compile (even better: report the compilation errors).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants