[Haskell-cafe] Platform Versioning Policy: upper bounds are not our friends

[Ketil Malde]

"Bryan O'Sullivan" <bos at serpentine.com> writes:

> I propose that the sense of the recommendation around upper bounds in the
> PVP be reversed: upper bounds should be specified *only when there is a
> known problem with a new version* of a depended-upon package.

Another advantage to this is that it's not always clear what constitutes
an API change.  I had to put an upper bound on binary, since 0.5
introduced laziness changes that broke my program.  (I later got some
help to implement a workaround, but binary-0.4.4 is still substantially
faster).  Understandably, the authors didn't see this as a breaking API
change.

So, +1.

-k
-- 
If I haven't seen further, it is by standing in the footprints of giants