You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any interest in bringing this support into vscode-clangd?
The only drawback is the clangd wasm file is currently weighing in at 90mb and it will need to be shipped with the extension to allow it to be served from the VS Code marketplace.
My first thought is that this is a different enough use case that it makes sense as a separate plugin. (If there's significant code to be shared, we could consider something like a different plugin living in the same repository, though I think the pace at which vscode-clangd changes is slow enough that a downstream model is not likely to be much overhead.)
@thegecko Do you have any idea of the performance impact on a regular environment using wasm compared to standard clangd executable?
Are there features that no longer work with wasm and/or serverless? I'm mainly thinking of loading of an index (both using remote server and file indexes)
@JVApen I'm sure there are going to be limitations regarding certain features, especially calling out to the outside world.
Performance impact should be negligible.
Based on the great work over at https://github.com/guyutongxue/clangd-in-browser I've been working on a VS Code extension which runs clangd entirely in the browser. This is useful for server-less environments such as https://vscode.dev.
Is there any interest in bringing this support into
vscode-clangd
?The only drawback is the clangd wasm file is currently weighing in at 90mb and it will need to be shipped with the extension to allow it to be served from the VS Code marketplace.
cc @HighCommander4
The text was updated successfully, but these errors were encountered: