`@match` gives the incorrect results when types are passed in as values about mlstyle.jl

[jariji]

That's like #127

[jonniediegelman]

I see. So Float64 is interpreted as just some variable for the right side to use in this case. This does indeed happen without types:

julia> one = 1; two = 2;

julia> x = two;

julia> @match x begin
           one => "One!"
           two => "Two!"
           _ => "Many!"
       end
"One!"

Maybe an error could be thrown if two patterns are the "same" on the left side?

[thautwarm]

I'd close this but pin it as it is a FAQ.
If anyone has a different idea, you could just have discussions here which is helpful for other users with this issue.

[jariji]

It's because in the first example those are literal patterns because they are 1 and 2, whereas Float64 is a capturing pattern because it's a symbol.

[ShalokShalom]

So can we close this one?

[ShalokShalom]

I would just include an appropriate error message?

[thautwarm]

I would just include an appropriate error message?

Do you have any design ideas? MLStyle can detect redundant patterns in some cases, but I'm not sure if I should mark things as intentional or unexpected.

[jariji]

Is there any benefit to allowing redundant cases (#127)?