Adam Azarchs

They _might_ accept it? https://github.com/facebook/zstd/issues/3123

Sure, attached here [BUILD.zstd.bazel](https://github.com/bazelbuild/rules_pkg/files/12731528/BUILD.zstd.txt). Note: 1. I didn't put any effort into checking whether it works on platforms besides linux/x64 2. I didn't enable support for features I don't need...

That would be nice, but mainly I think primarily people just want `fromdateiso8601` to be able to handle at least the subset of ISO-8601 date strings which are also compliant...

It looks like #8252 tried to fix this, but it doesn't seem to actually work. I haven't dug deep into why, but at least in my use case I'm using...

While an attribute would be great, even better would be to have the default level depend on compilation mode. That is, `-c opt` -> 9, `-c fast` -> 6 or...

Another possibility to bring up for some cases at least would be to compile the tools to WASM for embedding into the extension. That could work for e.g. `buildifier`/`buildozer` (although...

Compiling rust to wasm works really well actually; rust is probably the best possible language to use for wasm. But sure, maybe more trouble than it's worth. The benefit would...

The first error is because you don't have a wasm C++ toolchain configured for bazel. That isn't something I've tried before. The second error ``` you may need to enable...

> The resulting `starpls.wasm` is unfortunately rather big, with 16MB. I wonder if it has other unused dependencies that could be removed. Entirely-unused crates will generally be discarded at link...

I don't think it would work so well for a language server. It would, however, work great for e.g. `buildifier`, which can just communicate over stdio/stdout/stderr.