Closed michaelpj closed 1 week ago
A few things to think about:
NamedFieldPuns
or not? I would say "yes", since it's the closest to what RecordWildcards
does (it also relies on the field name matching the variable). So we would generate Foo{bar}
rather than Foo{bar=bar}
. This would require us to add the NamedFieldPuns
pragma, potentially.RecordWildcards
can appear in both expressions and patterns, we should support both.
Is your enhancement request related to a problem? Please describe.
Record wildcards implicitly bind the record field names. We can use inlay hints to display that information explicitly, and triggering it could insert an explicit binding for the field.
Describe the solution you'd like
becomes