Typo and markdown fixes
This commit is contained in:
parent
3f07abd4af
commit
2db13a7b41
2 changed files with 7 additions and 4 deletions
|
@ -1,4 +1,4 @@
|
|||
- file: posts/safe-prelude-a-thuought-experiment.md
|
||||
- file: posts/safe-prelude-a-thought-experiment.md
|
||||
title: "safe-prelude: a thought experiment"
|
||||
day: 2017-01-16
|
||||
- file: posts/foldable-mapm-maybe-and-recursive-functions.md
|
||||
|
|
|
@ -38,6 +38,7 @@ but wanted to play with this in the short term.
|
|||
* Use generalization (via type classes) when they are well
|
||||
established. For example: `Foldable` and `Traversable` yes,
|
||||
`MonoFoldable` no.
|
||||
|
||||
* _Controversial_ Avoid providing list-specific functions. This
|
||||
connects to the parent point. Most of the time, I'd argue that
|
||||
lists are _not_ the correct choice, and instead a `Vector`
|
||||
|
@ -84,7 +85,9 @@ Packages I considered but have not included yet:
|
|||
convinced everyone else uses it as much as I do. Also, there are some
|
||||
questions around generalizing its functions (e.g., `atomically` could
|
||||
be in `MonadIO`), and I don't want to make that decision yet.
|
||||
|
||||
* `stm-chans` falls into this category too
|
||||
|
||||
* `async` is an amazing library, and in particular the `race`,
|
||||
`concurrently`, and `Concurrently` bits are an easy win. I've left
|
||||
it out for now due to questions of generalizing to
|
Loading…
Reference in a new issue