Export Natural type from prelude
carter.schonwald at gmail.com
Wed Jul 7 21:17:04 UTC 2021
I’ll have a look when I have time in a few days.
On Wed, Jul 7, 2021 at 5:16 PM Carter Schonwald <carter.schonwald at gmail.com>
> Yeah. This is a good point.
> It’s worth doing a grep of definitions in hackage to see wha the blast
> radius is ofothwreiee working code. If there’s no breakage risk for old
> code, that’s a point in favor of inclusion of Natural in prelude rather
> than just being an extra import from base. If not, it’s a cost that must
> be weighed.
> On Wed, Jul 7, 2021 at 3:09 PM Henning Thielemann <
> lemming at henning-thielemann.de> wrote:
>> On Wed, 7 Jul 2021, Ken T Takusagawa wrote:
>> > On Fri, 2 Jul 2021, Carter Schonwald wrote:
>> >> This seems long overdue and aside from some redundant import warnings
>> likely low breakage risk
>> > Am I understanding correctly that this will cause any code
>> > that defines its own type named Natural to break?
>> > And the proper workaround will be
>> > import Prelude hiding(Natural)
>> > ?
>> this would work, but would cause warnings in older Prelude versions
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libraries