Supun Setunga

Running the tests on an emulator was one option. But with what Bastian suggested, we don't really need an emulator there, we can rely on the FVM to provide the...

I like this lightweight version more. The biggest concern I had with the original proposal was the UX/composability. But by limiting the purity requirement to only pre/post conditions, and by...

One more thing to consider/think about is the covariance/subtype checking between pure/impure functions. Might be a good reference: D-lang has pure functions: https://dlang.org/spec/function.html#pure-functions.

We only added it to the exporting (https://github.com/onflow/cadence/pull/1762). I think we still need to add it for importing as well. i.e: JSON -> cadence value

Thanks for reporting this. Yes, there is room for improvement here. At the moment resource invalidation happens at two stages: 1) Statically - when the code is deployed 2) Dynamically...

Probably it has meant to say that, for transactions, only **signed** transactions can get the auth account. i.e: each signer is passed as an argument to the `prepare` block. Maybe...

Thank you @psiemens for spending time to test the feature and for the feedback! 🙏 The test-framework provides two approaches for testing: - Integration tests - Unit tests **Integration tests**...

Added these to the improvements list: https://github.com/onflow/cadence/issues/1889

Yeah, makes sense. The current challenge is to support this within the existing cadence syntax/semantics. For e.g: imagine the test script imports `Foo` and `Bar`, where Foo imports `Baz` in...

Yeah, this is a problem with the TypeID encoding/decoding. As you may know, earlier cadence-json format used to encode type-information as a string (say jsoncdc `V1`), but later it was...