2039586 - Simplify the xpcom_async crate

Status: RESOLVED FIXED

(MailNews Core :: Networking: Exchange, task)

Description

[Brendan Abolivier [:babolivier]]

The xpcom_async crate was initially built with the idea that XpComFuture could be expanded to other XPCOM types than nsIChannel. This isn't exactly trivial, and we don't really have a need for that, and the crate's timer handling already deviate from that design. It should be (lightly) refactored to better represent what the crate actually is: a grab bag of utilities to bridge async XPCOM with async Rust.

Comment 1

[Brendan Abolivier [:babolivier]]

Attachment: Bug 2039586 - Part 1: Replace generic XpComFuture with AsyncChannelOpener. r=#thunderbird-back-end-reviewers

Comment 2

[Brendan Abolivier [:babolivier]]

Attachment: Bug 2039586 - Part 2: Rename xpcom_async into xpcom_async_glue. r=#thunderbird-back-end-reviewers

The main reason I've made this change is because I was told some time ago the
name of this crate was confusing when coming to the outside, and meant the crate
could be confused with an async runtime.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/6e3518cecc3d
Part 1: Replace generic XpComFuture with AsyncChannelOpener. r=edicharry
https://hg.mozilla.org/comm-central/rev/b8acdfc311e1
Part 2: Rename xpcom_async into xpcom_async_glue. r=edicharry