According to InfoWorld News, to improve the go language development tool, go may get its own language server, similar to Microsoft and Red Hat Language Server protocol.
The message is streamed out of the discussion group of the Go language developer, so this is not the final list of improvements.
The improvement plan is as follows:
Use tools such as the language server IDE to index and display information about code and packages. One participant said: Microsoft's Language server protocol is considered a good starting point because of its extensive support in the editor and IDE. The protocol is designed to be multiple languages integrated across the Code Editor and IDE.
Set up a standard "counter" API that can report statistical data.
Rewrite part of the Go assembly code.
To compensate for the gap between the Assembly and go, consider rewriting the Go encryption code. For performance reasons, the encryption code in the language is often written in assembly language, but the assembly code is difficult to debug, maintain, and read. One participant said: instead of using go to rewrite the encryption code, it makes maintenance easier and improves the encryption performance of Go.
Extend the Math/bits package in Go1.9 to accommodate overrides. Math/bits Package bitwise operations are optimized.
Refactor garbage collection and related tools at the compiler and runtime to reduce the load on the core tools and the IDE.
Embed the compiler in the IDE for a quick syntax check.
Compiling the memory code is helpful for repairing the environment where the system files are missing, and the programmer can run the test continuously.
The discussion group also proposes adjustments that include dependency management and interface issues. It was suggested that critical fixes to the packages in the standard library tended to wait for a new version release time of 6 months, and better dependency management might help to migrate some packages from the standard library to their own projects.
In addition, the use of the standard library interface and some other problems have been carried out, and made the relevant recommendations. Please refer to the original text for details.
Http://www.oschina.net/news/87743/how-googles-go-language-could-be-improved
Go language If you follow this improvement, can you fire over Java?