That's not inherent to generics - see Swift, which absolutely allows protocols to require static/class members or initializers. Swift 3 also adds generic type a

That's not inherent to generics - see Swift, which absolutely allows protocols to require static/class members or initializers. Swift 3 also adds generic type aliases (typedefs). Having worked extensively with both I think Swift learned a lot from C# (and many other languages). As for Concepts... No one seems to be able to agree on them so I'm not holding my breath.