~jack/jackkelly-name

1559b1b2c628b68a2b8f0066213545ce2c947f20 — Jack Kelly 2 years ago b55df28
Haskell/Reflex app: Clarify some points
1 files changed, 5 insertions(+), 4 deletions(-)

M content/blog/0130-a-static-haskell-reflex-frontend-app.markdown
M content/blog/0130-a-static-haskell-reflex-frontend-app.markdown => content/blog/0130-a-static-haskell-reflex-frontend-app.markdown +5 -4
@@ 85,7 85,7 @@ stack.

* I ran into two GHCjs problems with random Hackage libraries -
  `casa-abbreviations-and-acronyms` was trying to build binaries that
  depended (ultimately) on `network` (which uses the C FFI), and
  depended (indirectly) on `network` (which uses the C FFI), and
  `monoid-subclasses` was depending on implementation details of
  `Text` to make some of its instances go fast. Each needed drive-by
  PRs to add GHCjs conditionals, and while the maintainers of both


@@ 96,9 96,10 @@ stack.
* The types used by
  [`reflex`](https://hackage.haskell.org/package/reflex) and
  [`reflex-dom`](https://hackage.haskell.org/package/reflex-dom) are
  pretty gnarly. Partial type signatures and typed holes are necessary
  to navigate this, but there's an art in giving GHC enough
  information that it begins to say something useful.
  pretty gnarly. Partial type signatures and typed holes are an
  indispensable navigation aid, but there's an art to giving GHC
  enough information that it can get started. Otherwise, it can't
  infer anything of value and the error messages are useless.

* Nix makes it easy to pull random branches into a Haskell package
  set, _provided that you understand how the Nix Haskell