rfc:structural-typing-for-closures
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| rfc:structural-typing-for-closures [2023/04/20 16:11] – nicolasgrekas | rfc:structural-typing-for-closures [2023/04/20 16:16] (current) – 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? Could this be cached internally? | * 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? Could this be cached internally? | ||
| - | * Should reflection know something about this? | + | * Should reflection/'' |
| - | * In order the achieve the required check, the engine would need to autoload the interface/ | + | * In order the achieve the required check, the engine would need to autoload the interface/ |
| ===== Future Scope ===== | ===== Future Scope ===== | ||
| * Auto-cast closures to interfaces that have a single method that is not necessarily named '' | * Auto-cast closures to interfaces that have a single method that is not necessarily named '' | ||
| - | * Allow closures to declare the interface they implement as in e.g. '' | + | * Allow closures to declare the interface they implement as in e.g. '' |
| ===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== | ||
rfc/structural-typing-for-closures.1682007088.txt.gz · Last modified: 2023/04/20 16:11 by nicolasgrekas