|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7 |
|
| #
ab78bd82 |
| 22-Mar-2026 |
Ho Kim <[email protected]> |
fix: correct various typos (#12807)
Signed-off-by: Ho Kim <[email protected]>
|
|
Revision tags: v43.0.0 |
|
| #
5afb6030 |
| 03-Mar-2026 |
Nick Fitzgerald <[email protected]> |
Fix error chaining and casting with `anyhow` errors in the chain (#12705)
* Fix error chaining and casting with `anyhow` errors in the chain
Fixes https://github.com/bytecodealliance/wasmtime/issue
Fix error chaining and casting with `anyhow` errors in the chain (#12705)
* Fix error chaining and casting with `anyhow` errors in the chain
Fixes https://github.com/bytecodealliance/wasmtime/issues/12690
* add cfg that got lost
* avoid raw identifiers
* Add missing cfg for test function
show more ...
|
| #
4fd25c07 |
| 27-Feb-2026 |
Alex Crichton <[email protected]> |
Fix using `downcast` with `anyhow::Error` (#12689)
* Fix using `downcast` with `anyhow::Error`
Previously when converting `wasmtime::Error` into `anyhow::Error` it
ended up breaking the `downcast`
Fix using `downcast` with `anyhow::Error` (#12689)
* Fix using `downcast` with `anyhow::Error`
Previously when converting `wasmtime::Error` into `anyhow::Error` it
ended up breaking the `downcast` method. This is because
`anyhow::Error::from_boxed` looks like it does not implement the
`downcast` method which is how all errors were previously converted to
`anyhow::Error`. This commit adds a new vtable method for specifically
converting to `anyhow::Error` which enables using the typed construction
methods of `anyhow` which preserves `downcast`-ness.
* Add a test showcasing anyhow-source behavior
show more ...
|
|
Revision tags: v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2 |
|
| #
bc4582c3 |
| 27-Jan-2026 |
Alex Crichton <[email protected]> |
Forbid rustdoc warnings in CI (#12420)
* Forbid rustdoc warnings in CI
This commit corrects our handling of rustdoc flags in CI to ensure that
warnings indeed fire. Additionally this changes our fl
Forbid rustdoc warnings in CI (#12420)
* Forbid rustdoc warnings in CI
This commit corrects our handling of rustdoc flags in CI to ensure that
warnings indeed fire. Additionally this changes our flags to pass
`-Dwarnings` to ensure that we have warning-free doc builds when all
features are enabled at least.
There were quite a lot of preexisting issues to fix, so this
additionally goes through and fixes all the warnings that cropped up.
* Update nightly toolchain again
prtest:full
* Update another nightly
* Fix a warning in generated code
show more ...
|
|
Revision tags: v41.0.1, v36.0.5, v40.0.3 |
|
| #
8325e1ec |
| 23-Jan-2026 |
Alex Crichton <[email protected]> |
Fold the `wasmtime-error` crate into `wasmtime-core` (#12418)
Similar to #12398 and #12407 the idea is that all our dependency-free
(mostly) data structures and foundational data-types are in one lo
Fold the `wasmtime-error` crate into `wasmtime-core` (#12418)
Similar to #12398 and #12407 the idea is that all our dependency-free
(mostly) data structures and foundational data-types are in one location
to centralize testing, ergonomics, documentation, idioms, etc.
show more ...
|