Closed bgamari closed 5 months ago
One question is how this should be versioned until the next release is made. I would suggest that the version of clash-prelude
be bumped such that downstream users can rely on CPP to guard existing orphans.
One question is how this should be versioned until the next release is made. I would suggest that the version of clash-prelude be bumped such that downstream users can rely on CPP to guard existing orphans.
The next release (for 1.8) will be 1.8.2, which should be guardable using MIN_VERSION_clash_prelude
.
@kloonbot run_ci dbed0535843345a9634196d33b6d4f88283b04ad
I only now realize what you were saying: you want to bump the version on master to reflect the API changes. We haven't done this before, and IMO this is a bit too much overhead for development. If you want a more principled discussion I'd suggest opening a Discussions thread. For now this LGTM, and I'll merge it!
Both I and
clash-protocols
have found this instance useful, leading to overlapping instances. Let's put it where it belongs.Still TODO: