Constructors that require arguments shouldn't be in patterns without arguments

[Negabinary]

Constructors that require arguments shouldn't be in patterns without arguments

[disconcision]

hmm.. would need to decide what the error should be. the example shown doesn't seem fatally problematic, in that even if someone believed X gets bound by the let, it would still have the same result. but if the type had another constructor say Y of the same type, then it would be more confusing. in principle though in such cases would have refutable pattern errors, assuming it's possible to do refutability for arrow typed things

[disconcision]

probably just an arity error for constructors in patterns would do it?

[Negabinary]

It's probably more problematic in a case statement:

An arity error would probably do it; we just need to pass some sort of "expected arity" through pattern statics

[disconcision]

not sure we need any more information. we know constructor arities from types in ctx. so:

1. for pattern ap statics, check if fun pos is constructor with arrow type. inline its statics (ie dont recurse on funpos)
2. for pattern constructor statics, it must be non arrow type (since we know we didnt pass thru ap)