odersky

That's not clearer, and requires more explanations. Where does the `Self` come from?

My proposal is irrelevant for people reading the code. `typeclass` is just one more thing to learn, with no associated benefit.

Imagine the ridicule: Only scala has "types" _and_ "classes" _and_ "typeclasses", but in fact "typeclasses" are neither types nor classes, they are traits! No, that won't fly.

I hesitated a lot between `is` and `has`. Both are appropriate in some circumstances and less so in others. It also depends on the type class name. For instance, here...

`Swift` [does have OO inheritance](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/inheritance/) and it uses `Self`.

Swifts protocols are very close to what this proposal implements. Also, we do have as precedent the `:` for context bounds. If I write `x: Int` the informal reading of...

This is a test PR, to see what breaks in the CB.

It turns out nothing broke. I only had to change - some tests that explicitly tested the old behavior - a typo in a shapeless 3 test which was not...

That's the problem: The example we got (and handled) was already very specialized. Who wants a monad _and_ a traversable in the same function? But what's much more common is...

I think this needs to be merged, and I will not have the bandwidth to make a SIP for this. Are there other opinions how to proceed here?