Daniel Sainati

> But I think program cache argument is a good one. Do you have any idea how will it look when contract dependency graph is used? Yeah. Currently the program...

> @dsainati1 I think you mean dependency graph of all contracts on chain, not the contract got updated right? This is an implementation detail I think. We would only need...

> Do you mean _references_ in "once a reference has been moved" and "once the underlying reference is moved"? We do not currently track references statically. Oh yea I definitely...

I think the proposed run-time enforcement would solve the security footgun but would also probably make the language worse overall in the long run. Generally any kind of error that...

Now that https://github.com/onflow/flow/pull/1056 has been merged in a more limited form than originally proposed, discussion on this FLIP should resume imo. Based on the discussion on that FLIP, it seems...

Paraphrasing a discussion from slack: My general thoughts on this are that there is diminishing returns in working on improving error reporting. Once you reach a certain level of clarity,...

> As an average developer what I will gain from this ? This will actually make it simpler, not harder, to think about your code. Reasoning about how and when...

After some internal discussion, we identified one potential alternative approach to this that would be significantly more lightweight than the idea in the main FLIP. This version would only be...

> I guess the "Breaking Change" label can be removed, as the latest version of the proposal is just an addition? > > Or is changing conditions to only allow...

We do load only the runtime type info here, the actual stored value itself is not loaded.