I'm just finalizing the material for my http://Scala.one Advanced Type Mechanics course, but all my examples use "foo", "bar" and "baz" and I want to use some less clichéd terms... What alternatives would you suggest? I'll give you credit if this ever makes it into a book!
-
There's a real downside to using more specific examples, in that people come to associate them with just that specific domain, and not like something universal. I've given meaningful names to the examples where I can. Now I just want some original names that don't infer context.
As for the other things you mention, these are all important, but they're not the primary focus of the course, and it's quite full already! But I'm certainly going to cover some compile-time performance characteristics.
-
-
Anyway, it will be wonderful course and you will complete work started by
@ktosopl http://ktoso.github.io/scala-types-of-types/ … . I hope that next step will be a more advanced course that explains how types help to reach a mechanical sympathy (when hardware and software working together in harmony) -
I wish I had remembered that existed sooner! It would have given me some useful exhaustivity hints...
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.