Move orphan instances to a separate package

[sol]

No description provided.

[RyanGlScott]

If you create the sol/base-orphans repo, I'd be willing to port over the existing orphan instances from base-compat.

[sol]

Hey, sorry to be slow on this. I'll do it tomorrow. Alternatively, if you want to have it under your account I'm fine with that too.

Sent from my iPhone

On 16 Apr 2015, at 1:06 am, Ryan Scott notifications@github.com wrote:

If you create the sol/base-orphans repo, I'd be willing to port over the existing orphan instances in base-compat.

—
Reply to this email directly or view it on GitHub.

[RyanGlScott]

We do have quite a collection of compatibility packages now (base-compat, base-orphans, setenv, my mtl-compat package, etc.). Mind if I create a GitHub group (e.g., haskell-compat) and eventually move all of these repos there?

[sol]

Sounds good!

Sent from my iPhone

On 16 Apr 2015, at 1:47 am, Ryan Scott notifications@github.com wrote:

We do have quite a collection of compatibility packages now (base-compat, base-orphans, setenv, my mtl-compat package, etc.). Mind if I create a GitHub group (e.g., haskell-compat) and eventually move all of these repos there?

—
Reply to this email directly or view it on GitHub.

[RyanGlScott]

I did a quick port of the orphan instances in this repo to base-orphans. Can you review it when you get a chance? One thing I'm a bit indecisive about is the name of the exported module (I dubbed it BaseOrphans for now).

[sol]

Yes, I was puzzled about that, too. I had Data.Orphans in mind.

[RyanGlScott]

I guess if we had to classify under which top-level module name in base the notion of orphan instances would fall under, Data probably makes the most sense. I'll change it as a part of a pull request I'm working on.

[sol]

@RyanGlScott I'll remove the orphans from base-compat now, or are you already on it?

[RyanGlScott]

I'm a bit busy at the moment, so go ahead.