Zalim Bashorov
Zalim Bashorov
Here is what it looks like For Wasm For JS
Possible improvements #### Wasm #### JS
> Would you like to make a pull request with this change? Not anytime soon, so I'd appreciate it if someone could take it and fix it.
@murfel 2. Overriding `name` for custom errors is normal practice[[1]] and improves DX. Often, it also implies inheritance, but I think it could be omitted in simple cases. Could you...
> In current implementation it can clash with standard error names - it's what we should avoid Well, we can consider using a qualified name, but it may look unusual...
> Default expectation - some constant and unique name like "UnhandledKotlinWasmCoroutinesError" A runtime usually writes something like "Uncaught Exception", everything else should be visible from the stacktrace.
Normally, we should throw the original exception, but IIRC it doesn't work well for pre 2.2.20 compiler, with 2.2.20-Beta2+ it should be good.
> We could add a new wasm-merge flag, perhaps like wasm-merge --final-exports=WILDCARD. Specifying the list at link-time is similar to e.g. Emscripten's EXPORTED_FUNCTIONS, but it might be very long. It...
> We want to annotate exports, not functions - functions can have multiple exports, making this ambiguous otherwise. Custom annotations lacks that atm. I think being able to annotate declarations...
@fitzgen, we have a bunch of micro and macro benchmarks at https://kotl.in/wasm-benchmarks. But another challenge could be that compilers using the GC proposal also use the EH proposal. Fortunately, for...