Supun Setunga

@nvdtf Can you please check if this still the case? I tried with the CLI `v1.15.0-cadence-v1.0.0-preview.13` (there are even newer versions, so maybe try with the latest), and I could...

@onflow/cadence Being able to borrow with `&{NonFungibleToken.Collection}` was a bit of a surprise, because the old value was linked as: ```cadence self.account.link( self.CollectionPublicPath, target: self.CollectionStoragePath ) ``` But thinking about...

> I guess that applies to both values migrated from pre-1.0 and values created in 1.0? yes

In my view, it is correct to say that any function with `access(contract)` can only be accessed by the contract interface itself only. I guess what we are looking for...

I was thinking we should even reject interface default functions with `access(contract)`, because right now its a bit inconsistent/confusing. i.e: they would have to be public

I think what's happening here is the created account `foo` is on the `blockchain`, whereas the composite type creation `CompositeType("A.0000000000000005.Foo.ContractInitialized")` happens off-chain (in the test script). So the account is...

The implementation is available in this [closed] PR: https://github.com/onflow/cadence-tools/pull/8. But unfortunately, it was never merged, because of some tech-dept at the time, where these tools were moved to a separate...

Implemented and deployed

I can take over this one

>I think would be nice to have some examples on this. I remember running into some cases when updating nft/ft code bases to match C1.0, e.g: https://github.com/onflow/flow-nft/blob/f741cb5352f1889984e60437e0805b8371dcd7fe/contracts/ExampleNFT.cdc#L157C34-L157C41 where it would...