Now that ContractId’s can be stored in Sets and Maps are there any plans to allow them to be part of a the key spec for another contract? This would allow the uniqueness and existence of the contract to determine other contracts as opposed to that contract’s payload, which we one may want to duplicate (and not introduce another id concept).
1 Like
Unfortunalty, there is no plan to allow the contract IDs in contract keys. Without going into too much details, here are some the main reasons:
1 - We are not 100% sure we can actually make it work.
2 - This would take quite a bit of effort, at least as much as what we had to invest to allow contract IDs in the Map. We prefer to invest this effort in other features we believe more important.
3 - This would interfers with some optimization we have or plan to have.
3 Likes
@Remy Just curious to know whether this has changed at all since the last reply?
It has not, you can follow Support for Contract Ids in Contract Keys · Issue #9497 · digital-asset/daml · GitHub if you want to be aware of changes.
1 Like