<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in lib.rs</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>c3a6060b - Polyfill `ToWasmtimeResult` and add eventually-necessary call sites (#12308)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#c3a6060b</link>
        <description>Polyfill `ToWasmtimeResult` and add eventually-necessary call sites (#12308)* Polyfill `ToWasmtimeResult` and add eventually-necessary call sitesThis commit polyfills `wasmtime_internal_error::ToWasmtimeResult` in`wasmtime_environ`, adds the cargo feature plumbing that will eventually connectto the `&quot;wasmtime_internal_error/anyhow&quot;` cargo feature but for now justconfigures this polyfill, and adds uses of the polyfill at all the sites thatwill be necessary once we swap out `anyhow` for`wasmtime_internal_error`. Currently, the polyfill is just an identity function,because `wasmtime::Result`/`wasmtime_environ::error::Result` is just anothername for `anyhow::Result`. Once we do move away from `anyhow`, however, thatwill no longer be the case, and these uses will do the necessary conversion.My goal with landing this as an incremental commit is to make it so that theactual commit that does the error crate swap out can be as close to _just_ the`Cargo.toml` dependency change, without any other code changes as much aspossible. This, in turn, means that swap out should be super easy to revert, ifnecessary.* Add a couple more `.to_wasmtime_result()` invocations in fuzz code* Revert &quot;Add a couple more `.to_wasmtime_result()` invocations in fuzz code&quot;This reverts commit b33696e5f63f7eed731ca9dad10fec5e55a550d3.* Move cranelift fuzz targets back to anyhow* Fix cargo feature enablement for explorer

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Tue, 13 Jan 2026 18:04:34 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d634dffa - Migrate explorer to `wasmtime::error` (#12262)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#d634dffa</link>
        <description>Migrate explorer to `wasmtime::error` (#12262)

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Wed, 07 Jan 2026 21:36:53 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>4c8edb95 - More clearly flag internal crates as such (#10963)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#4c8edb95</link>
        <description>More clearly flag internal crates as such (#10963)* More clearly flag internal crates as suchThis commit is an attempt to more clearly flag internal crates in thisproject as internal and not intended for external use. Specifically:* Many crates are renamed from `wasmtime-foo` to  `wasmtime-internal-foo`.* All of these crates now have `INTERNAL: ...` in their crates.io  description.* All of these crates now have a warning at the top of their  documentation discouraging use.This change is a result of rustsec/advisory-db#1999 where the goal is tobe crystal clear from a project perspective that usage of these cratesare highly discouraged and not supported. We&apos;ll still probably get suchadvisories but we won&apos;t be considering them CVEs from the project itselfdue to the internal nature of these crates and the discouragingwarnings.Some concrete changes used here are:* Inter-crate dependencies still use `wasmtime_foo` for naming and do  so with Cargo&apos;s package-renaming features.* Crate renames are specified at the workspace level so the rename is  only in one locations and all other inherit it.* Contribution documentation now has some brief guidelines about crate  organization.* Update vet config* Update checks for wasmtime-fiberprtest:full* Update publish script* Another fiber rename* Fix some doc tests

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Fri, 06 Jun 2025 21:13:36 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>90ac295e - Update Wasmtime to the 2024 Rust Edition (#10806)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#90ac295e</link>
        <description>Update Wasmtime to the 2024 Rust Edition (#10806)* Update Wasmtime to the 2024 Rust EditionNow that our MSRV supports the 2024 edition it&apos;s possible to make thisswitch. This commit moves Wasmtime to the 2024 Edition to keepup-to-date with Rust idioms and access many of the edition featuresexclusive to the 2024 edition.prtest:full* Reformat with the 2024 edition

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Mon, 19 May 2025 16:40:55 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>ede670dd - CLIF in explorer (#8972)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#ede670dd</link>
        <description>CLIF in explorer (#8972)* clif in wasmtime explore* clif in wasmtime explore: do not continue if clif directory exists* clif in explorer: run prettier* explorer: use flex instead of width* explorer: fix scrolling* explorer: use temp directory for clif* explorer: tempfile is an optional dependency* clif in explorer: do not display clif if compiling with winch

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Tue, 23 Jul 2024 16:41:43 +0000</pubDate>
        <dc:creator>Vulcain &lt;100216770+vulc41n@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>896e25e3 - upgrade to wasm-tools 0.211.1 (#8838)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#896e25e3</link>
        <description>upgrade to wasm-tools 0.211.1 (#8838)* upgrade to wasm-tools 0.211.1* code review* cargo vet: auto imports* fuzzing: fix wasm-smith changes* fuzzing: changes for HeapType* Configure features on `Parser` when parsing---------Co-authored-by: Alex Crichton &lt;alex@alexcrichton.com&gt;

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Fri, 21 Jun 2024 14:48:21 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
<item>
        <title>f9946472 - Show function names in explore tool instead of only function indices (#8639)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#f9946472</link>
        <description>Show function names in explore tool instead of only function indices (#8639)* Implement runtime::Module::function_locations_with_names()Map the iterator returned by Module::function_locations() to anotherone that returns a 3-tuple containing the function name, the offset,and the length of each function defined in this particular module.* Show function names in &quot;explore&quot; instead of just the indices* Address review: Change iterator format* Address review: use the new iterator struct* Address review comments

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Tue, 21 May 2024 17:27:52 +0000</pubDate>
        <dc:creator>L. Pereira &lt;l.pereira@fastly.com&gt;</dc:creator>
    </item>
<item>
        <title>9ec02f9d - Decouple `serde` from its `derive` crate (#6917)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#9ec02f9d</link>
        <description>Decouple `serde` from its `derive` crate (#6917)By not activating the `derive` feature on `serde`, the compilation speedcan be improved by a lot. This is because `serde` can then compile inparallel to `serde_derive`, allowing it to finish compilation possiblyeven before `serde_derive`, unblocking all the crates waiting for`serde` to start compiling much sooner.As it turns out the main deciding factor for how long the compile time of aproject is, is primarly determined by the depth of dependencies ratherthan the width. In other words, a crate&apos;s compile times aren&apos;t affectedby how many crates it depends on, but rather by the longest chain ofdependencies that it needs to wait on. In many cases `serde` is part ofthat long chain, as it is part of a long chain if the `derive` featureis active:`proc-macro2` compile build script &gt; `proc-macro2` run build script &gt;`proc-macro2` &gt; `quote` &gt; `syn` &gt; `serde_derive` &gt; `serde` &gt;`serde_json` (or any crate that depends on serde)By decoupling it from `serde_derive`, the chain is shortened and compiletimes get much better.Check this issue for a deeper elaboration:https://github.com/serde-rs/serde/issues/2584For `wasmtime` I&apos;m seeing a reduction from 24.75s to 22.45s whencompiling in `release` mode. This is because wasmtime through `gimli`has a dependency on `indexmap` which can only start compiling when`serde` is finished, which you want to happen as early as possible sosome of wasmtime&apos;s dependencies can start compiling.To measure the full effect, the dependencies can&apos;t by themselvesactivate the `derive` feature. I&apos;ve upstreamed a patch for`fxprof-processed-profile` which was the only dependency that activatedit for `wasmtime` (not yet published to crates.io). `wasmtime-cli` andco. may need patches for their dependencies to see a similarimprovement.

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Tue, 29 Aug 2023 16:02:06 +0000</pubDate>
        <dc:creator>Christopher Serr &lt;christopher.serr@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>af7ef8df - Fix some minor issues with the `explorer` command (#5988)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#af7ef8df</link>
        <description>Fix some minor issues with the `explorer` command (#5988)This commit fixes a few minor issues that Nick and I ran into walkingthrough some code with the `wasmtime explore` command:* When a new function is reached the address map iterator is advanced  past the prior function to avoid accidentally attributing instructions  across functions.* A `&lt;` comparison was changed to `&lt;=` to fix some off-by-one  attributions from instructions to wasm instructions.* The `skipdata` option is enabled in Capstone to avoid truncating  AArch64 disassemblies too early.

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Sat, 11 Mar 2023 02:31:31 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>9ed441e6 - Introduce the `wasmtime-explorer` crate (#5975)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/explorer/src/lib.rs#9ed441e6</link>
        <description>Introduce the `wasmtime-explorer` crate (#5975)This implements Godbolt Compiler Explorer-like functionality for Wasmtime andCranelift. Given a Wasm module, it compiles the module to native code and thenwrites a standalone HTML file that gives a split pane view between the WAT andASM disassemblies.

            List of files:
            /wasmtime-44.0.1/crates/explorer/src/lib.rs</description>
        <pubDate>Sat, 11 Mar 2023 00:33:06 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
