Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[FEATURE REQUEST] Archive for Daml Interfaces
See original GitHub issueI confirm that, if this is a feature request that has security implications, I already contacted security@digitalasset.com and followed the responsible disclosure policy.
I confirm that this is not a question or a request for technical support by the community, for which the Daml forum is available.
What is the problem you want to solve?
Given that all implementations of interfaces are templates, it is surprising that the archive function does work on them. It would improve the UX a fair amount if one didn’t have to declare functions
archive_IMyInterface : ContractId IMyInterface -> Update ()
in each interface and then implement them using archive on each interface implementation.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I still think we want this feature. I don’t mind waiting a little, but targeting 2.6 would be a good thing imo.
I think there is a need for this but I’d recommend to not rush this. I discussed making Archive a “builtin” choice with @remyhaemmerle-da and I’d do it as part of that rather than just generating it from the compiler.