Type checking should have a friendly error for partial applied constructors

[jdunkerley]

Goal one:
If I have a constructor with missing required fields but of the correct type for the function, we want to have a friendly error message.

Stretch:
Allow constructors of types which are convertible to target type to also have friendlier messages.

Idea is something like Filter_Condition type checking where we have a function passed then have to approve.

[JaroslavTulach]

following program:

from Standard.Base import all

type Complex
    Value a b c d

process (c:Complex) = c.a+c.b+c.c+c.d

main = process (Complex.Value 1 2 3)

yields

Type error: expected `c` to be Complex, but got Complex.Value[t.enso:4:5-17] a=1 b=2 c=3 d=_. Try to apply d argument.

Isn't that user friendly enough error message?

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2023-09-06):

Progress: - evaluating and closing: #7746 (comment)

• merged Delay check of suspended arguments until they are about to be computed #7727
• "use virtual threads framework": Language Server 2.0 #5419
• Arrow language: Arrow language to use industry standard format for columnar data #7755
• standups & meetings It should be finished by 2023-09-07.

Next Day: Bugfixing