Latest:
[ERT: 1m54s] Someone recently
suggested a way to make the barrier to using deprecated code even higher. He was
kidding, but I looked into how to make it work. Here is the result.
Recent:
[ERT: 1m8s]
Last week I published a paths library. I showed it to the Haskell subreddit and learned
from their reaction.
[ERT:
2m39s] Filepaths have been a pain in my neck for years. Paths are hard, overused,
misused and mostly unsafe. In this post I present a newly released library that serves
to make working with paths safer in the common use-case.
[ERT: 2m4s] Not
very long ago, I tried to use the GHC API to do some static analysis. It turned out to
be a lot more complicated than I expected. Now I was going to fix some of that.
[ERT: 1m54s]
Boolean blindness has been discussed over and over and over and over again. The
conclusion seems to be that always using Boolean values for decisions is a generally
bad idea and that using church encoded lambda calculus instead is not much better (and
impractical). Here are my two cents on the matter: Use evidence instead of Boolean
values.
[ERT:
3m21s] Values of custom types usually have invariants imposed upon them. In this post I
motivate and announce the validity, genvalidity and genvalidity-hspec libraries that
have just come out.
[ERT: 2m7s] It may come natural
to try and save money wherever we can, but I argue this may be a bad idea.
[ERT:
4m59s] Using arguments, configurations, settings, options or instructions in any
language can be a struggle. There are quite a few libraries to solve just this problem
and most of them involve either some global state or an object that is carried around
through the program. Seeing as neither of these options are feasible and scalable in
Haskell (when implemented naively), one has to think twice about how exactly to do it.
In this blogpost I propose a general scheme to deal with all of these.
[ERT: 3m38s] Yes, you
read that right. Not on Haskell, but in Haskell.
