4 ms·

> There are bugs like https://github.com/swc-project/swc/issues/2038 https://github.com/swc-project/swc/issues/2038 that haven't been fixed after a few years.

by magnio 2y ago

> There are bugs like https://github.com/swc-project/swc/issues/2038 https://github.com/swc-project/swc/issues/2038 that haven't been fixed after a few years. I tried all those examples on the swc playground[0] and all of them pass, so the issue seems to be fixed, but maybe they forgot to close it. By the way, swc, oxc, and biome all pass test262. [0]: https://swc.rs/playground https://swc.rs/playground (version 1.6.5)

rty32 2y ago
Their documentation says "passes almost all tests": https://rustdoc.swc.rs/swc_ecma_parser/ https://rustdoc.swc.rs/swc_ecma_parser/ Which could be outdated as well. But if that's true, it's the problem isn't it? If some of the most important information about a critical part of the toolchain isn't up-to-date, how can I have confidence in this? (Also for my specific use case, I need to set an ecmascript version, something that is common in JS based parsers, but it's not available in swc ecma parser. At least I didn't find it.) For context, I contributed to acorn to fix an issue I found while using it in one of my projects. But that happened because I extensively used acorn in the first place. I don't quite have the confidence to adopt these Rust based tools yet.