Alex Crichton (Sep 18 2026 at 00:50): Alex Crichton (Sep 18 2026 at 00:50):In the last component-model meeting we settled on wasm32-webp2 as a target name, and
Alex Crichton (Sep 18 2026 at 00:51):er, hit too soon. Anyway I opened an issue in rust-lang/rust to create the target there and there's feedback -- https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/Create.20a.20new.20tier.203.20target.3A.20.60wasm32-webp.E2.80.A6.20compiler-team.231037/near/625110012 -- that the target name may want to have "component" in the name somewhere. Subjectively I like the current name, but Ryan/Ben would y'all be able to write down (here's fine I can transfer it over there) some rationale y'all were thinking?
Ben Visness (Sep 18 2026 at 13:14):I'm sure one of us can post a response there this morning, I've been reading it now and then to see how the discussion has gone. I'll draft something up and just run it by Ryan before posting.
Victor Adossi (Sep 21 2026 at 09:40):Tiny tiny thought, but cm (Component Model) might also be a good triple part to have rather than comopnent.
I know meaningful target triplets might be somewhat of a bedtime story, but it feels like the component model is the thing being targeted here, and the word "component" doesn't really capture it.
"cm" is a jump but "what does cm mean in this context" leads more directly to I think what people would want to know about the target rather than "what does component mean"
Ben Visness (Sep 21 2026 at 14:28):I would happily support an eventual naming scheme of wasm32-web-cm if that's where things end up.
Alex Crichton (Sep 29 2026 at 21:49):To follow-up on this the wasm32-webp2 name has been approved, so once things are sorted/published out in wasi-libc/wasi-sdk/component-sdk I'll add the target
Last updated: Oct 11 2026 at 02:20 UTC