Sure. But I wouldn't do that for 1.0 of the lang. It sounds quite feasible to add support for that in 1.x if the community needs it. There's a reasonable path to upgrade to http/2 while spending more effort into what's critical for the lang to get to 1.0.

[Edit] And it's quite feasible to decide later that http/2 was never needed for this usecase.

Sure, but GP was saying "out of scope" in a way that sounded like "forever, for this use-case", not just "for 1.0". I may have misinterpreted

The package manager is designed to download archives (.tar.gz) of packages, not the composite files.

Most source code packages, including their metadata, are generally small even as an aggregated compressed file, and it's very common to download a lot of them all at one time once you've resolved the necessary dependencies. It depends on several factors though -- including community ones (are lots of tiny packages encouraged?) and how things like the build system work when downloading things.

In practice, it's very much an appropriate use case for multiplexing, if you ask me. But not having it isn't a dealbreaker either, IMO. It's a bit more work to support HTTP/2 and can be done rather transparently later on anyway, since the underlying transport can be switched and has an upgrade path.

> are lots of tiny packages encouraged?

Very much the opposite