Zsolt Bölöny
Zsolt Bölöny
The OpenTelemetry SDK specification defines a [JaegerRemoteSampler](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#jaegerremotesampler), which was supported in [jaeger-client-cpp](https://github.com/jaegertracing/jaeger-client-cpp.git) but missing from `opentelemetry-cpp`.
The README mentions `unit_t::to` and `unit_cast` for accessing the underlying value as `T`. However the implementation of these seem to be using `static_cast` internally, and (due to an `unit_t::operator T()`...
(Follow up of https://github.com/gfx-rs/gfx/pull/3499) Although the DX12 backend sets the debug name of `CommandBuffer`s by calling `SetName` on the underlying `GraphicsCommandList`, it doesn't show up in the tested graphics debuggers...
Fixes the `Code Checks (formatting, clippy)` GitHub action.
Adds support for WebAssembly SIMD, using the currently available stable intrinsics in Rust. I also added a GitHub action for automated testing. Benchmarking also works, and shows a ~3x improvement...
During development my method of testing (other than running `cargo test` of course) was to run the demo on a sample OBJ file and compare its output with the original....
The C++ implementation can target WebAssembly with vertex buffer decoding/filtering and index buffer decoding, which are needed for the `EXT_meshopt_compression` glTF extension, supported by e.g. `three.js` and `Babylon.js`. Given Rust's...
The C++ implementation has hand-rolled x86 (SSSE3, experimental AVX512), ARM (NEON) and WebAssembly SIMD accelerated vertex buffer decoding and filtering. As of Rust 1.27 there's [standardized support](https://doc.rust-lang.org/edition-guide/rust-2018/simd-for-faster-computing.html) for x86 SIMD...