Bug Description:

No react code is required anymore, we can have .ts extension instead of .tsx.

Steps to Reproduce:

Minimized code

trait CLibrary {
  @native
  def foo(x: Int): Unit
}

object I9432 {
  def main(args: Array[String]): Unit = {
    new CLibrary {
      override def foo(x: Int): Unit = println(x)
    }.foo(1)
  }
}

Output

$ java -version
openjdk version "11.0.8" 2020-07-14

$ C:\opt\dotty-0.26.0-RC1\bin\dotc.bat -deprecation -feature -d target\c

cc rust-lang/rls#1112
cc microsoft/language-server-protocol#376

This causes problems with displaying correct diagnostic span and code suggestion spans (here).

Document the commands that clients should implement and their expected behaviour on https://github.com/eclipse/eclipse.jdt.ls/wiki/JDT-LS-Extensions

Environment data

VS Code version: 1.34.0
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: Ubuntu 19.04
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used: virtualenv

Problem

The type hints in the stub file for the current module aren't used for autocompletion.

I have a foo.pyi file as

Motivation

Currently the language server stores symbols (i.e. variables, classes, ...) in two locations:

• The source path, containing the parsed .kt source files from the user's workspace
• The [class path](https://github.com/fwcd/kotlin-language-server/blob/master/server/

Completion items list can now use items, as implemented in jupyterlab/jupyterlab#8140. We should take use of that as this is very low-effort high-gain feature. Currently the first letter and a colour code is used to indicate completion type. It will make it easier and more efficient to choose the right completion.

Costs:

• We need to bring the icons. The types/icon set

https://github.com/mawww/kakoune/releases/tag/v2019.07.01

With version 0.4.1, we set the server capabilities to include text on save

But we always process the files from disk. Until such time as we actually use that text, we should not ask for it.

I feel like there is a bunch of people trying out the language server and it's not working for them, often because of missing configuration or installs. In the long term it would be great to improve error messages in these cases.

As a first step I think it would help to provide documentation for troubleshooting.

• How to collect information / logs and report them (e.g. in vs code or vim)