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
Currently, writing validation code to convert from versioned Cedarbridge types to application types involves a ton of boilerplate. Being able to pattern match will reduce some of this, but some of it will remain. The language knows all of the types that are going to need to be converted, so it could generate some empty classes filled with static methods that need to be filled in.
The text was updated successfully, but these errors were encountered:
This introduces UUIDs as a standard type, and introduces
a convenience module for the runtime in order to reduce
the amount of boilerplate required for users.
Fix: #32
Affects: #31
Currently, writing validation code to convert from versioned Cedarbridge types to application types involves a ton of boilerplate. Being able to pattern match will reduce some of this, but some of it will remain. The language knows all of the types that are going to need to be converted, so it could generate some empty classes filled with static methods that need to be filled in.
The text was updated successfully, but these errors were encountered: