Daniel Sainati

> Problem here was type system, ex: extended2 will be subtype of base or not ? In the FLIP as it is currently, `extended2` would be type `Base with Extras,...

> Cadence is acting little bit unreliable here in my opinion, .... We just merged interface default conditions. Default interface conditions are not quite the same thing as full method...

> One thing I'm curious of is that if multiple "Extension developers" make an NFT extension with overlapping functions, would a resource be allowed to extend both of those? Yes;...

To summarize the discussion here for those following along, currently the largest point of debate is over whether or not extending a resource should change its type. The two models...

> Also there is a breaking situation when R decides to implement I in the future. I think we need to clear up how resources will behave in that situation....

For the example with `elem.setCustomValidity` why do you need to check its type? The return of `document.querySelector('input')` is defined as `HTMLInputElement | null` so you should only need to check...

This is on our radar but at the moment it isn't a priority. We are working on a large restructuring of Flow's type inference, and one of the side effects...

I would recommend just suppressing it where it occurs. It is safe to do so because error suppressions using the `method-unbinding` code will not catch any errors other than this...

Is this proposing that interfaces would inherit events from each other, but composites wouldn't inherit from interfaces? That seems inconsistent; the behavior for the two should be the same.

I was referring to @joshuahannan's question above; if the events are defined in `Receiver` and `Provider` but emitted from `Vault` and `Collection`, how would these subtype interfaces access the supertypes'...