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
With the latest implementation of type-safe bounds, the definition of a MultiIndexPK type is crucial, as it now serves to define the type of the (partial) bounds over the index key (the part that corresponds to the pk, that is). See https://github.com/confio/poe-contracts/pull/114/files#r812029191 for reference / an example.
Let's fix the docs to reflect this use case, and its importance.
Also, let's remove the default over PK that we introduced for backwards compatibility, as this type definition is now really important for specifying (type-safe) bounds.
The text was updated successfully, but these errors were encountered:
With the latest implementation of type-safe bounds, the definition of a
MultiIndex
PK
type is crucial, as it now serves to define the type of the (partial) bounds over the index key (the part that corresponds to the pk, that is). See https://github.com/confio/poe-contracts/pull/114/files#r812029191 for reference / an example.Let's fix the docs to reflect this use case, and its importance.
Also, let's remove the default over
PK
that we introduced for backwards compatibility, as this type definition is now really important for specifying (type-safe) bounds.The text was updated successfully, but these errors were encountered: