Simon Zünd 9911fd13cc [torque-ls] Add prototype language server implementation for Torque ... Design Doc: https://goo.gl/9G9d9k The initial prototype consists of a few parts: The VS Code extension is now built using TypeScript. The build artifact is checked-in along side the extension. The extension now starts up the language server when it is activated. The path to the LS executable is configurable via VS Code settings. The language server is a separate executable. It adds a light-weight object model on top of a Json Parser for reading/writing LSP requests and responses. The current server is very much bare-bones featurewise: - Tell the client that the server can handle "goto definition" - Recompile when Torque files change - Goto definition support for Macros/Builtins, local variables and arguments. R=mathias@chromium.org, mvstanton@chromium.org, tebbi@chromium.org Bug: v8:8880 Change-Id: Ie9b433e64ee63e9aa757b6bf71e5d52beb15b079 Reviewed-on: https://chromium-review.googlesource.com/c/1494354 Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#59960}		2019-03-01 09:30:47 +00:00
..
test-torque-ls-json.cc	[torque-ls] Implement basic Json parser for the language server	2019-02-26 07:38:03 +00:00
test-torque-ls-message.cc	[torque-ls] Add prototype language server implementation for Torque	2019-03-01 09:30:47 +00:00
test-torque.cc	[torque] make overload resolution robust concerning branching contexts	2019-02-15 10:04:36 +00:00