You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to start using the below syntax for open/constrained records:
{ a, b, .. } = data
and the following for closed records:
{ a, b } = data
This facilitates Roc devs being able to define closed records that will raise type errors if the destructured values get additional fields added. This is not possible in Roc today.
This change will probably break a good deal of existing Roc code that assumes that { a, b } destructures are open records, but the direction of this change precludes the ability to facilitate the transition with smart parsing + formatting.
The text was updated successfully, but these errors were encountered:
We want to start using the below syntax for open/constrained records:
and the following for closed records:
This facilitates Roc devs being able to define closed records that will raise type errors if the destructured values get additional fields added. This is not possible in Roc today.
This change will probably break a good deal of existing Roc code that assumes that
{ a, b }
destructures are open records, but the direction of this change precludes the ability to facilitate the transition with smart parsing + formatting.The text was updated successfully, but these errors were encountered: