Suboptimal error message when matching on a tuple struct using a private constructor about rust HOT 4 OPEN

hm. It's not clear to me why the version you initially went with isn't permitted.

from rust.

hm. It's not clear to me why the version you initially went with isn't permitted.

I'm not an expert, so I might be wrong, but my guess is that falls out from it being a minor SemVer change to convert between tuple and normal structs if all fields are private.

from rust.

That seems plausible. The usual semantic of .. in this case is to ignore all other subfields, however, so I guess what I'm really asking is why we can't match on structs with Struct(..) in general.

from rust.

I suppose we could want some immediately-adjacent syntactic space for variadics that would block off this being a logical conclusion.

from rust.