Substrate

#swift-core-team #protocols
Improving the UI of generics
Improving the UI of generics
We could think of type-level-abstracted return types as doing the same thing but at the type level; you give a function generic arguments as inputs, and it gives a certain return type back. ​ This roughly follows the progression of `impl Trait` in Rust, where it was first introduced only for return types, then was generalized to be able to appear structurally in both argument and return types. We think this is a reasonable first step because it directly addresses the biggest functionality gap in the generics model. After that first step, there are a few fairly orthogonal language change discussions we can have, some of which are already underway
·forums.swift.org·
Improving the UI of generics
“Defining an addition and multiplication doesn’t make the thing a Ring—there are axioms that need to be satisfied. Protocols are not just bags of syntax.”
“Defining an addition and multiplication doesn’t make the thing a Ring—there are axioms that need to be satisfied. Protocols are not just bags of syntax.”
Defining an addition and multiplication doesn’t make the thing a Ring—there are axioms that need to be satisfied. Protocols are not just bags of syntax. https://t.co/pLdUxdnxR3— 🎃 Spooky ABI Stability 🎃 (@stephentyrone) March 5, 2019
·twitter.com·
“Defining an addition and multiplication doesn’t make the thing a Ring—there are axioms that need to be satisfied. Protocols are not just bags of syntax.”