Alice 55589e941f net/fetch: Don't write Response::termination_reason in closure (#42572) ...

Writing `termination_reason` in the closure in `http_network_fetch()`
had no effect, as the response is captured by value, and cannot be
captured by mutable reference as it is needed later in the outer
function.

This is flagged as a warning with Rust 1.92:


https://github.com/servo/servo/actions/runs/21750902723/job/62748597306?pr=42402

Note: I don't understand this code deeply, I was just trying my best to
fix the warning. I'm more than happy to close this PR or change the code
if someone more familiar has a better idea of how to fix it.

Testing: Existing tests, no behaviour change.

Signed-off-by: Alice Boxhall <alice@igalia.com>

2026-02-12 16:58:56 +00:00

..

cors_cache.rs

Update rustfmt to the 2024 style edition (#35764)

2025-03-03 11:26:53 +00:00

fetch_params.rs

Implement pending preload responses with futures (#40059)

2026-01-04 12:22:54 +00:00

headers.rs

script: Fix handling of invalid fetch responses for link stylesheets (#42037)

2026-01-24 10:39:58 +00:00

methods.rs

net/fetch: Don't write Response::termination_reason in closure (#42572)

2026-02-12 16:58:56 +00:00