- Bigger code on lambda syntax page
- Need some stuff here (on the slide before lambda typing)
- Colours on new types page.
- Missing type param on BiFunction on streams types page.
- To vs Too on stream oprs page.
- "Thnigs" on Bad - Inconsistent API page
- Red on Bad was hard to read - Partial Application Page
- (Making up Range) on Bad Type inference
- About 30 minutes
- Does that mean that the max arity of a closure is 2?!? Why did they give them such javaish names?
- Is there a sequence for a list of optionals?
- Why so much hate on flatmap? Just the type inference stuff?
- No control over parallelism but things have side effects everywhere? That's nuts?
- map only works on list. fmap is the functor one.
- Have some kind of diagram for compose to show what it does. I think that this is really important.
- Dupe slides in function composition
- Again diagram to explain linesLongerThan100 function.
- bug in first slide for compose code. Needs a $
- Unfortunately, I'd remove the Jesse Ventura slide.
- Should probably make the actual point that some point free is good but you can go too far.
- Examples of input and output of functions would be handy.
- Explaining folds is not that easy. You'll likely want a diagram or something. Remember tony took an entire talk to explain folds. (You should rewatch tony's talk!)
- Bout 30 minutes also