rfc:structural-typing-for-closures

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:structural-typing-for-closures [2023/04/13 16:05] nicolasgrekasrfc:structural-typing-for-closures [2023/04/13 16:09] nicolasgrekas
Line 46: Line 46:
   * What would be the performance impact of adding this feature to the language, considering the engine would need to verify the closure signatures at runtime?   * What would be the performance impact of adding this feature to the language, considering the engine would need to verify the closure signatures at runtime?
   * Should reflection know something about this?   * Should reflection know something about this?
 +
 +===== Future Scope =====
 +
 +  * Auto-cast closures to interfaces that have a single method that is not necessarily named ''%%__invoke()%%''
 +  * Allow closures to declare the interface they implement as in e.g. ''function () implements FooInterface {}''
  
 ===== Proposed Voting Choices ===== ===== Proposed Voting Choices =====
rfc/structural-typing-for-closures.txt · Last modified: 2023/04/20 16:16 by nicolasgrekas