> > That's ugly, and more typing. The actual user-and-documentation-friendly way would > be > > for it to reset "cart1" each time there's a device that adds another slot. This > > reinforces that it's the same kind of cart slot each time. > > That's literally the stupidest thing I've seen all week and falls apart like a house > of cards the moment you start dealing with systems that have multiple slots, which > can have devices added which themselves add multiple slots. Your proposal essentially > results in a parameter-ambiguity fuckfest.
Sure, it wouldn't work in a complex parameter-ambiguous situation (then you'd need to fall back to your syntax), but for the relatively common case of a chain of things with identical slots on both ends it does simplify things. It makes the easy things easier without further complicating the hard things.