Takeshi Yoneda
Takeshi Yoneda
found the Rust demangler https://github.com/alexcrichton/rustc-demangle/blob/master/src/v0.rs so maybe we could port this to C++ code here to provide better stack trace for Rust.
OK, that would be nice. just curious do we have any external dependency criteria here in Proxy-Wasm project like Envoy does?
I found that Rust binary somehow comes with both of C/C++ mangled symbols (starts with `_Z`) and Rust ones (starts with `_R`) together even if we enable the "v0" mangling...
Is emscripten C++ exception supported in the native Wasmtime or any other native WASI runtime? If so, I would like to see their implementation but I couldn't find :\
I see that emcc experimentally supports `-fwasm-exception` flag in LLVM(https://reviews.llvm.org/D67208) and the staging V8 has already implementation for that(https://bugs.chromium.org/p/v8/issues/detail?id=6577) based on the Wasm exception proposal. https://github.com/emscripten-core/emscripten/issues/11233#issuecomment-635332613
now the latest V8 has been shipped with Wasm's native exception proposal and the latest Emscripten support for that. Maybe worth a try
FYI, we could read secret emebedded in env vars once https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/126 and https://github.com/envoyproxy/envoy/pull/15009 are merged, though reading file functionality could also be helpful for users.
@PiotrSikora thoughts?
> Let's do that. Thanks! @mathetake any objections/comments? No objection! I think we've reached consensus now. Thanks!
rust: unknown, zig: freestanding, so either works for me