Simon Zünd 0dc3ffc566 [torque-ls] Move GlobalContext into LangServerData after compilation ... The language server needs Torque compilation artifacts like declarables for more advanced features. This CL moves the GlobalContext into the LanguageServerData class when Torque compilation finishes, to preserve all the compiler data. Additionally, all declarables are split up by source id. This makes providing all symbols of a file easier. R=tebbi@chromium.org Bug: v8:8880 Change-Id: I424d1ddc04fcd18934f76a736900bc5d08261c07 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1601132 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#61462}		2019-05-14 05:43:06 +00:00
..
earley-parser-unittest.cc	[torque] add unittest for Earley parser	2018-07-24 14:01:33 +00:00
ls-json-unittest.cc	Reland^3 "[torque] Throw exception instead of aborting if something goes wrong"	2019-04-16 10:41:20 +00:00
ls-message-unittest.cc	[torque-ls] Move GlobalContext into LangServerData after compilation	2019-05-14 05:43:06 +00:00
ls-server-data-unittest.cc	[torque-ls] Move GlobalContext into LangServerData after compilation	2019-05-14 05:43:06 +00:00
torque-unittest.cc	Reland "[torque] Introduce force_assert_statements compiler option"	2019-05-08 09:01:41 +00:00
torque-utils-unittest.cc	[torque-ls] fix Windows file paths	2019-04-24 08:17:07 +00:00