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
One strength not previously mentioned is that dynamically typing allows a convenient way to scrape for inehrents a la #130 (comment)
An alternative strongly typed approach would be to have each tuxedo piece provide an type to be aggregated. Simple pieces may have no types (and use ()) or a single type (like Coin) and use it directly. More complex pieces may have multiple types and will provide an enum themselves.
The text was updated successfully, but these errors were encountered:
This issue is to discuss the strengths and weaknesses of the current way in which UTXO are dynamically typed.
The thoughts are explained mostly in the docs for the
dynamic_typing
module.One strength not previously mentioned is that dynamically typing allows a convenient way to scrape for inehrents a la #130 (comment)
An alternative strongly typed approach would be to have each tuxedo piece provide an type to be aggregated. Simple pieces may have no types (and use
()
) or a single type (likeCoin
) and use it directly. More complex pieces may have multiple types and will provide an enum themselves.The text was updated successfully, but these errors were encountered: