LSP tripping out

[waalge]

What Git revision are you using?

#1094
a nix patch on latest release v1.1.11

What operating system are you using, and which version?

nixos

Describe what the problem is?

I tried

      let Input(oref, Output{ address, .. }) = input

and it said

I tripped over a confusing constructor destructuring [aiken::check::syntax::unused_record_fields]
2. Try instead: 
   
   ╰─▶ Input { output: oref, output_reference: Output { address, .. } } [aiken::check::syntax::unused_record_fields]

Also, a reoccurance of the LSP suggesting you pull in Script from crypto rather than address.

Think its trying to be too clever?

What should be the expected behavior?

I'm tired ... but this looks super odd.

[rvcas]

Thanks, I'm going to do a round of LSP improvements soon

[waalge]

Another one

1. I struggled to unify the types of two expressions.
    [aiken::check::type_mismatch]
2. I am inferring the following type:
   
       (Address, Value, Datum, List<Input>)
   
   but I found an expression with a different type:
   
       (Address, Value, Datum, List<Input>)
   
   Either, add type-annotation to improve my inference, or adjust the expression to have the expected type. 

---

The above could definitely be more helpful.
Its not using my use .../types as t alias. The first of the Datums should be t.Datum.