0dc9b63ed3
Macros are now inaccessible from CSA except if their declaration is marked with the "export" keyword. The implicit field accessors for class fields are always exported. In this CL, unwarranted access from CSA is prevented by appending a pseudo-random suffix to non-exported names. This is to be replaced by something more principled, namely by not including these macros at all in the headers included from CSA. Bug: v8:7793 Change-Id: I3ffb2e91a616623f81b4b4508e001ad0cf65d2c2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1615258 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#61672} |
||
---|---|---|
.. | ||
.vscode | ||
out | ||
src | ||
syntaxes | ||
.npmrc | ||
language-configuration.json | ||
package.json | ||
README.md | ||
tsconfig.json | ||
tslint.json |
Torque support
This extension adds language support for the Torque language used in V8.
Installation
Since the extension is currently not published to the marketplace, the easiest way to install the extension is to symlink it to your local extension directory:
ln -s $V8/tools/torque/vscode-torque $HOME/.vscode/extensions/vscode-torque
Additionally, for advanced language server features, the extension needs to be built locally (the syntax highlighting does not require this step). The following needs to be run everytime the extension is updated:
cd $V8/tools/torque/vscode-torque
npm install
Language server
The language server is not built by default. To build the language server manually:
autoninja -C <output dir> torque-language-server
The default directory where the extension looks for the executable is "out/x64.release",
but the absolute path to the executable can be configured with the torque.ls.executable
setting.