aboutsummaryrefslogtreecommitdiffstats
path: root/third_party/WebIDL/tests/test_arraybuffer.py
diff options
context:
space:
mode:
authordependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>2025-04-29 17:22:42 +0000
committerGitHub <noreply@github.com>2025-04-29 17:22:42 +0000
commite79520c25a221c3c8be492de8251abcf8a6651e9 (patch)
tree972a9ac949f6de3e81d545429abdb9b61144aa90 /third_party/WebIDL/tests/test_arraybuffer.py
parent830a850f106790cf53084dbd6ed35aca901e02c6 (diff)
downloadservo-main.tar.gz
servo-main.zip
build(deps): bump bytemuck from 1.22.0 to 1.23.0 (#36754)HEADmain
Bumps [bytemuck](https://github.com/Lokathor/bytemuck) from 1.22.0 to 1.23.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Lokathor/bytemuck/blob/main/changelog.md">bytemuck's changelog</a>.</em></p> <blockquote> <h1><code>bytemuck</code> changelog</h1> <h2>1.23</h2> <ul> <li><code>impl_core_error</code> crate feature adds <code>core::error::Error</code> impl.</li> <li>More <code>ZeroableInOption</code> impls.</li> </ul> <h2>1.22</h2> <ul> <li>Add the <code>pod_saturating</code> feature, which adds <code>Pod</code> impls for <code>Saturating&lt;T&gt;</code> when <code>T</code> is already <code>Pod</code>.</li> <li>A bump in the minimum <code>bytemuck_derive</code> dependency from 1.4.0 to 1.4.1 to avoid a bug if you have a truly ancient <code>cargo.lock</code> file sitting around.</li> <li>Adds <code>Send</code> and <code>Sync</code> impls to <code>BoxBytes</code>.</li> </ul> <h2>1.21</h2> <ul> <li>Implement <code>Pod</code> and <code>Zeroable</code> for <code>core::arch::{x86, x86_64}::__m512</code>, <code>__m512d</code> and <code>__m512i</code> without nightly. Requires Rust 1.72, and is gated through the <code>avx512_simd</code> cargo feature.</li> <li>Allow the use of <code>must_cast_mut</code> and <code>must_cast_slice_mut</code> in const contexts. Requires Rust 1.83, and is gated through the <code>must_cast_extra</code> cargo feature.</li> <li>internal: introduced the <code>maybe_const_fn</code> macro that allows defining some function to be const depending upon some <code>cfg</code> predicate.</li> </ul> <h2>1.20</h2> <ul> <li>New functions to allocate zeroed <code>Arc</code> and <code>Rc</code>. Requires Rust 1.82</li> <li><code>TransparentWrapper</code> impls for <code>core::cmp::Reverse</code> and <code>core::num::Saturating</code>.</li> <li>internal: Simplified the library's <code>fill_zeroes</code> calls to <code>write_bytes</code></li> </ul> <h2>1.19</h2> <ul> <li>Adds the <code>#[track_caller]</code> attribute to functions which may panic.</li> </ul> <h2>1.18</h2> <ul> <li>Adds the <code>latest_stable_rust</code> cargo feature, which is a blanket feature that turns all other features on that are both sound and compatible with Stable rust.</li> </ul> <h2>1.17.1</h2> <ul> <li>Adds <code>#[repr(C)]</code> to the <code>union Transmute&lt;A, B&gt;</code> type that's used internally for most of the transmutations.</li> </ul> <h2>1.17.0</h2> <ul> <li>Makes the <code>must_cast</code> versions of the by-value and by-ref casts be <code>const</code>. The mut ref cast is unaffected for now (mut references aren't yet stable in <code>const fn</code>). This increases the MSRV of using that particular feature from 1.57 to 1.64.</li> </ul> <h2>1.16.3</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Lokathor/bytemuck/commit/028ff3bec68ab9c123dc578b74a7af4a72a37609"><code>028ff3b</code></a> chore: Release bytemuck version 1.23.0</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/343f34ff9ef4084bb06516862d6e24f43172ca85"><code>343f34f</code></a> changelog</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/90db36000f622d0a9c5b678812ccadd96823248a"><code>90db360</code></a> Impl core's Error trait on Rust 1.81+ (<a href="https://redirect.github.com/Lokathor/bytemuck/issues/311">#311</a>)</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/ede91413f72e77b8e061a6da1da2bc6df739b3a2"><code>ede9141</code></a> Set rust version for <code>bytemuck_derive</code> to 1.61 (<a href="https://redirect.github.com/Lokathor/bytemuck/issues/310">#310</a>)</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/46d0910f3a3a9850319a2f64291407b2289493e4"><code>46d0910</code></a> Extend <a href="https://redirect.github.com/Lokathor/bytemuck/issues/308">#308</a> with <code>-unwind</code> support (<a href="https://redirect.github.com/Lokathor/bytemuck/issues/309">#309</a>)</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/6751adc3e40aa71ee22abfd19b97769b40d1f280"><code>6751adc</code></a> Impl ZeroablInOption for several function types. (<a href="https://redirect.github.com/Lokathor/bytemuck/issues/308">#308</a>)</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/66569e6cc7b3c7a7edadeb80219aa23386ed7554"><code>66569e6</code></a> chore: Release bytemuck_derive version 1.9.2</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/5c301b1ddd02afe41d6ccf37396630da415f7457"><code>5c301b1</code></a> remove resolver from the Cargo.toml</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/3053413e55eb300caf8a2254e37928c5270b3bc0"><code>3053413</code></a> update the .cargo/config.toml to use the &quot;stable rust&quot; feature.</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/9b087bb7e5192b71a3e0ec49571a60106266f0a5"><code>9b087bb</code></a> chore: Release bytemuck_derive version 1.9.1</li> <li>Additional commits viewable in <a href="https://github.com/Lokathor/bytemuck/compare/v1.22.0...v1.23.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bytemuck&package-manager=cargo&previous-version=1.22.0&new-version=1.23.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Diffstat (limited to 'third_party/WebIDL/tests/test_arraybuffer.py')
0 files changed, 0 insertions, 0 deletions