Recently, I've found myself wanting to make changes to code that works
inside code where TyCons are knot-tied [1]. But I've found myself unable to
make much progress, since my ability to debug this code is severely limited
by the fact that I can't seem to trace anything. That is, if I try tracing
I definitely agree with what you're saying around some of the features that
require external support such as backpack.
I think my statement was focused more on new language features that don't
require additional support, as with stack getting access to those is as
simple as hopping on the latest
Hi!
On 2017-08-03 at 08:41:59 +0200, Ara Adkins wrote:
[...]
> I nevertheless see `stack` as a huge boon for easing adoption of new
> compiler versions (and hence new language features/extensions).
Since I totally disagree about Stack being beneficial to the quick
adoption of new features,
Glad I could provide some useful thoughts!
> You are to some extent correct; an unwillingness to release before major
> (for some definition of "major") bugs are fixed will inevitably lead to
> slips. However, I think a faster release cycle will make it easier to
> accept releases with such bugs
