I find another way to import wasm code inside audioworklet context by using processorOptions (specs). The data is available via options inside the audioworkletnode.

class WhiteNoiseProcessor extends AudioWorkletProcessor {
  constructor(options) {
    super();
    const bufferSrc = new Uint8Array(options.processorOptions.data);
    WebAssembly.instantiate(bufferSrc, {}).then((res) =>
      console.log("res: ", res.instance.exports)
    );
  }

And in rust, you do it like that:

const WASM: &[u8] = include_bytes!("processor_bg.wasm");
        let data_proc = ProcData { data: WASM };
        let mut options = AudioWorkletNodeOptions::new();
        options.processor_options(Some(&Object::from(
            JsValue::from_serde(&data_proc).unwrap(),
        )));
        let worklet_node = AudioWorkletNode::new_with_options(&self.ctx, "noise", &options)?;

It works at least in Chrome 87 and FF 83

If we were discussing a run-of-the-mill open-source project, then issues like this would not spark such debate, I'd fork & be done with it. We’re talking about a far-reaching monopoly standard here. Vigorous community response should be cultivated because we care.

@J0eCool

1. Note how much of that is present in musl libc, not directly in emscripten. (Second most used is tests/third_party)

Yes, the nod was to how much its used in C in general.

2. Source level constructs are not the same as bytecode instructions

Of course, what we’re discussing is an internal concern that impacts source level constructs. That's part of the frustration, the black box should not leak its concerns.

3. Emscripten is not at the same level of abstraction as the wasm standard, so, no it shouldn't be reconsidered on that basis.

The point was that you will find gotos in majority of sizeable C projects, even within WebAssembly toolchain at large. A portable compiler target for languages in general that is not expressive enough to target its own compilers is not exactly consistent with the nature of our enterprise.

Specifically, it might be useful today to rewrite the gotos out of libc, because then we'd have more control over the resulting cfg than trusting relooper/cfgstackify to handle it well.

This is circular. Many above have raised serious unanswered questions regarding the infallacy of such a requirement.

We haven't because it's a nontrivial amount of work to wind up with wildly divergent code from upstream musl.

It is possible to remove gotos, as you said, it’s nontrivial amount of work! Are you suggesting everyone else should wildy diverge code paths because gotos should not be supported?

Emscripten developers (last I checked) tend to be of the opinion that a goto-like structure would be really nice, for those obvious reasons, so are unlikely to drop it from consideration, even if it takes years to reach an acceptable compromise.

A glimmer of hope! I’d be satisfied if goto/label support were taken seriously with a roadmap item + official invitation to get the ball moving, even if years out.

This is a particularly asinine statement.

You’re right. Forgive the hyperbole, I am a bit frustrated. I love wasm, and use it often, but I ultimately see a road of pain in front of me if I want to do anything noteworthy with it, like port TCC. After reading all the comments and articles, I still can't figure if the opposition is technical, philosophical or political. As @neelance expressed,

“Could someone in charge of V8 confirm in this thread that the opposition against irreducible control flow is not influenced by V8's current implementation?

I am asking because this is what bugs me most. [...]

If you guys listen to any of use, take @neelance’s feedback regarding Go 1.11 to heart. That’s hard to argue with. Sure, we can all do the nontrivial dusting of goto, but even then, we take a serious perf hit that can only be fixed with a goto instruction.

Again, forgive my frustration, but if this issue is closed without proper address, then I’m afraid it will send the wrong kind of signal that will only exasperate these kind of community responses and is inappropriate for one of the greatest standards efforts of our field. It goes without saying that I am a huge fan and supporter of all on this team. Thank you!

Wasm design choices that forbid arbitrary jumps are core to its philosophy. It is unlikely it can support gotos without something like funclets, for the same reasons it does not support pure indirect jumps.

@penzn Why is the funclets proposal stuck? It exists since October 2018 and it is still in phase 0.

What @jakobkummerow said. Specifically, see here for a sketch of the extension that would allow direct nesting of aggregates, as in C. The main reason for leaving it out of the MVP is that it requires introducing inner references in some form or another. It also allows the shape (interleavings of boxed and unboxed slots) of a heap value to become arbitrarily complex, so a typical GC will need type-like object descriptors to make them scale efficiently.

Note that for the MVP, an additional restriction on the above grammar is that array fields must be mutable.

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• Test (nightly)
• Test (beta)
• Test (stable)
• Fuzz (raw)
• Fuzz (wasm-opt-ttf)
• Fuzz (watgen)
• Fuzz Crate
• Fuzz Crate
• Fuzz (raw)
• Fuzz (wasm-opt-ttf)
• Fuzz (watgen)
• Test (nightly)
• Test (beta)
• Test (stable)

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• Test (nightly)
• Test (beta)
• Test (stable)
• Fuzz (raw)
• Fuzz (wasm-opt-ttf)
• Fuzz (watgen)
• Fuzz Crate
• Fuzz Crate
• Fuzz (raw)
• Fuzz (wasm-opt-ttf)
• Fuzz (watgen)
• Test (nightly)
• Test (beta)
• Test (stable)

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

Updates the requirements on wasmparser to permit the latest version. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/d3cbb38f990280861438d12c8a4546423fbc9ae6"><code>d3cbb38</code></a> Exception handling support (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/141">#141</a>)</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/b451461e6721b6a1df6e3f5ab794481ccfe6cfdd"><code>b451461</code></a> Remove incorrect example in the README.md (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/140">#140</a>)</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/84452f345e23c6ec9bf511af47b8e76ce1d36103"><code>84452f3</code></a> Bump wasmprinter version</li> <li>See full diff in <a href="https://github.com/bytecodealliance/wasm-tools/compare/wasmparser-0.67.0...wasmparser-0.68.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #191.

Updates the requirements on wasmparser to permit the latest version. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/7c534ccd1d52b29ea5fd50e4766bd9d6f20923b2"><code>7c534cc</code></a> Bump wasmparser to 0.69.1</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/3c511a634cc8ebe89626d908d629e1666b2015cf"><code>3c511a6</code></a> Fix a mismatch issue in nested wasm module validation</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/12ca74543d336cae6ab2972029a017574b862279"><code>12ca745</code></a> wasmparser version 0.69.0 (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/159">#159</a>)</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/864816a820ca40431cfe813bb7cfba5162578274"><code>864816a</code></a> Check memory index in attomics operations (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/156">#156</a>)</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/3ec9e0597a7a82c1a0b2a3804cb97a5d2c456ed1"><code>3ec9e05</code></a> Fail if non-funcref table used in call_indirect (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/157">#157</a>)</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/6b38d3b66ae86f28cbe9d4e378549371f76bc0c3"><code>6b38d3b</code></a> Update encoding of optional module linking import fields</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/acaf952aa0159cdbc31bf89dce62d35ed74d0b20"><code>acaf952</code></a> Fix event lookup for validating throw/br_on_exn (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/154">#154</a>)</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/8f0f049016ee42f32ff27c599ccab7c295ba1352"><code>8f0f049</code></a> Bump wasm-smith to 0.1.12</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/7aaa4533de8fd0ffa37d4c464a85ec83216c5b3e"><code>7aaa453</code></a> wasm-smith: add some additional configuration options.</li> <li><a href="https://github.com/bytecodealliance/wasm-tools/commit/74be3f64000bf964a33cdd4765c45c09f3344fc8"><code>74be3f6</code></a> Handle shorthands in alias instance references (<a href="https://github-redirect.dependabot.com/bytecodealliance/wasm-tools/issues/149">#149</a>)</li> <li>Additional commits viewable in <a href="https://github.com/bytecodealliance/wasm-tools/compare/wasmparser-0.67.0...wasmparser-0.69.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Bumps wasmparser from 0.35.3 to 0.68.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/bytecodealliance/wasm-tools/commits/wasmparser-0.68.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #524.

Bumps wasmparser from 0.35.3 to 0.69.1. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/bytecodealliance/wasm-tools/commits/wasmparser-0.69.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Hi all, To put some concrete numbers on the potential performance benefits of non-nullable types, I ran some experiments on our V8 prototype. Our prototype already optimizes away null checks if the static type of the object is known to be non-nullable.

I created a loop which repeatedly applies an operation requiring a null check on a local value. I measured the running time of the loop when the value was nullable vs. non-nullable. To isolate the effect of the operation from the loop jump and counter increment, I also ran an empty loop (which just increments a counter).

Note that, since the operation was always run on the same non-null object, the branch prediction should have hit every time. The results might be different otherwise.

Unfortunately, the benchmark is quite flaky, but these are the trends which I observed: For ref_test and ref_cast the normalized speedup (subtracting the running time of the empty loop) was about 13-19%. For struct_get and array_len it was about 33%. For struct_set about 50%. For array_get (with a constant index) about 67%. Of course, speedups were lower when the total time of the loop used instead, and ranged between 12-50%.

These numbers are of course specific to the situation of a tight loop with a specific payload, and are not likely to be measured in an actual program. However, I think they do show that non-nullability is an effective feature.

Bumps serde_json from 1.0.57 to 1.0.59. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>v1.0.58</h2> <ul> <li>Add serde_json::Map::remove_entry, matching the equivalent API on BTreeMap</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/64bb3962bd70ae74d6e8a9daa496504c64033760"><code>64bb396</code></a> Release 1.0.59</li> <li><a href="https://github.com/serde-rs/json/commit/9b64e0b17ca73e7fbecace37758ff19bc35dea05"><code>9b64e0b</code></a> Format with rustfmt 1.4.22-nightly</li> <li><a href="https://github.com/serde-rs/json/commit/d61505059766c0552e4798b3eaac227e2c56c563"><code>d615050</code></a> Filter floats that parse to infinity from as_f64</li> <li><a href="https://github.com/serde-rs/json/commit/b1ca6c718674e5d1f9f66f9cbe12b930f547fc0b"><code>b1ca6c7</code></a> Add test of as_f64 on large number</li> <li><a href="https://github.com/serde-rs/json/commit/d6eae8ffc06f242872bfe0f49e4e38a8f58381f0"><code>d6eae8f</code></a> Release 1.0.58</li> <li><a href="https://github.com/serde-rs/json/commit/9c38871ed942a9d87063d14cf91e5e8f738a5aab"><code>9c38871</code></a> Add no-std preserve_order check in CI</li> <li><a href="https://github.com/serde-rs/json/commit/e8bb41c94c77cc89fa31a36fa539c4dcc5d7d894"><code>e8bb41c</code></a> Fix no-std preserve_order build</li> <li><a href="https://github.com/serde-rs/json/commit/4e0d3499ce27fb54d7f225bcde7cf43094355387"><code>4e0d349</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/serde-rs/json/issues/712">#712</a> from dtolnay/remove_entry</li> <li><a href="https://github.com/serde-rs/json/commit/4c3300b1759168bb02c48e722e765a76add0ed1f"><code>4c3300b</code></a> Fix no-std build on rust <1.40</li> <li><a href="https://github.com/serde-rs/json/commit/187d89863abf67924d0b604d1b76cd62d86d0894"><code>187d898</code></a> Add CI builds on rust 1.40 and 1.45</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #731.

Bumps serde_json from 1.0.57 to 1.0.60. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>v1.0.60</h2> <ul> <li>Add <code>impl FromIterator<(impl Into<String>, impl Into<Value>)> for Value</code>, which collects a Value::Object (<a href="https://github-redirect.dependabot.com/serde-rs/json/issues/733">#733</a>, thanks <a href="https://github.com/matklad">@matklad</a>)</li> </ul> <h2>v1.0.59</h2> <ul> <li>In arbitrary_precision mode, return None from serde_json::Number::as_f64 if the JSON number is larger than the maximum possible f64</li> </ul> <h2>v1.0.58</h2> <ul> <li>Add serde_json::Map::remove_entry, matching the equivalent API on BTreeMap</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/6a4cd8d21879274f07baa3d35f6e5b2d43057986"><code>6a4cd8d</code></a> Release 1.0.60</li> <li><a href="https://github.com/serde-rs/json/commit/b9598ce50f3376eb48865711168757065bcd9a39"><code>b9598ce</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/serde-rs/json/issues/733">#733</a> from matklad/from-iter-of-pairs</li> <li><a href="https://github.com/serde-rs/json/commit/0c4b4dfc8ae8e6d32d3721567b6f26cc2e49cd5f"><code>0c4b4df</code></a> Allow collecting an iterator of pairs into JSON object</li> <li><a href="https://github.com/serde-rs/json/commit/efc910404a6c8863188e733a0809b594b52d11b4"><code>efc9104</code></a> Suppress clippy unnecessary_wraps lints</li> <li><a href="https://github.com/serde-rs/json/commit/bda64205e3abd2788d0e4006ceb94c7236da7c56"><code>bda6420</code></a> Resolve clippy comparison_to_empty lint</li> <li><a href="https://github.com/serde-rs/json/commit/ec7eeb6933670655b28862fe1571e17801cad788"><code>ec7eeb6</code></a> Suppress new manual_range_contains lint</li> <li><a href="https://github.com/serde-rs/json/commit/64bb3962bd70ae74d6e8a9daa496504c64033760"><code>64bb396</code></a> Release 1.0.59</li> <li><a href="https://github.com/serde-rs/json/commit/9b64e0b17ca73e7fbecace37758ff19bc35dea05"><code>9b64e0b</code></a> Format with rustfmt 1.4.22-nightly</li> <li><a href="https://github.com/serde-rs/json/commit/d61505059766c0552e4798b3eaac227e2c56c563"><code>d615050</code></a> Filter floats that parse to infinity from as_f64</li> <li><a href="https://github.com/serde-rs/json/commit/b1ca6c718674e5d1f9f66f9cbe12b930f547fc0b"><code>b1ca6c7</code></a> Add test of as_f64 on large number</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/json/compare/v1.0.57...v1.0.60">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>