Combine yields incompatible tuple types

[cdlm]

I was trying to extend your example to also accept #rgb colors, like so:

const rgb = mecha.convert(Rgb, Rgb.from, mecha.combine(.{
    mecha.char('#'),
    mecha.oneOf(.{
        rgbBytes,
        rgbNibbles,
    }),
}));
const rgbBytes = mecha.combine(.{ byte, byte, byte });
const rgbNibbles = mecha.combine(.{ nibble, nibble, nibble });
const byte = mecha.convert(u8, mecha.toInt(u8, 16), mecha.manyRange(2, 2, hex));
const nibble = mecha.convert(u8, mecha.toInt(u8, 16), mecha.manyRange(1, 1, hex));
const hex = mecha.digit(16);

And I'm getting this error when testing: error: expected type '.mecha.Result(.mecha.struct:323:23)', found '.mecha.Result(.mecha.struct:323:23)'
As far as I understand from the code and asking on Discord, combine generates its return type, but rgbBytes and rgbNibbles have distinct tuples even though they are both u8 triplets… (due to @TypeOf)

[cdlm]

I worked around it by un-factoring convert from rgb down to rgbBytes and rgbNibbles, so those become Parser(Rgb) and the unique tuple types are immediately consumed.

I'm still wondering if there isn't a better way, but feel free to close.

[Hejsil]

Good catch. I've pushed a fix that should force the compiler to cache the result of Tuple. I'll have to revisit this once 0.7.0 hits.

[cdlm]

👍
I can confirm it allows me to factor the conversion to Rgb back up :-)