You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For an in-depth treatment of types vs. classes, see the blog post
141
147
["There are more types than classes"](https://typelevel.org/blog/2017/02/13/more-types-than-classes.html).
142
148
143
149
### How can a method in a superclass return a value of the “current” type?
144
150
145
-
Possible solutions include F-bounded polymorphism (familiar to Java programmers),
146
-
type members, and the typeclass pattern.
147
-
148
-
[discussion of alternatives on Stack Overflow](https://stackoverflow.com/questions/59813323/advantages-of-f-bounded-polymorphism-over-typeclass-for-return-current-type-prob)
151
+
Possible solutions include F-bounded polymorphism
152
+
_(familiar to Java programmers)_, type members,
153
+
and the [typeclass pattern](http://tpolecat.github.io/2013/10/12/typeclass.html).
149
154
150
-
[blog post](http://tpolecat.github.io/2015/04/29/f-bounds.html) arguing against F-bounds and in favor of typeclasses.
155
+
This [blog post](http://tpolecat.github.io/2015/04/29/f-bounds.html)
156
+
argues against F-bounds and in favor of typeclasses;
157
+
see also [this Stack Overflow post](https://stackoverflow.com/questions/59813323/advantages-of-f-bounded-polymorphism-over-typeclass-for-return-current-type-prob) for some counterpoint.
151
158
152
159
### What does `<:<` mean?
153
160
154
161
It's a "type constraint", and it comes from the standard library,
0 commit comments