# Split base into GHC and non-GHC parts

**URL:** <https://discourse.haskell.org/t/split-base-into-ghc-and-non-ghc-parts/14339>\
**Category:** Core Libraries Committee\
**Created:** [June 30, 2026, 9:57pm UTC](https://discourse.haskell.org/t/split-base-into-ghc-and-non-ghc-parts/14339 "2026-06-30T21:57:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![augustss](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/augustss/32/887_2.png) [@augustss](https://discourse.haskell.org/u/augustss)\
**Post date:** [June 30, 2026, 9:57pm UTC](https://discourse.haskell.org/t/split-base-into-ghc-and-non-ghc-parts/14339/1 "2026-06-30T21:57:37Z")

</div>

A general comment. It would be nice if base was split into GHC and non-GHC parts. But I’m just day dreaming.

---

<div class="post-metadata">

**Author:** ![romes](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/romes/32/2912_2.png) [@romes](https://discourse.haskell.org/u/romes)\
**Post date:** [July 1, 2026, 12:53pm UTC](https://discourse.haskell.org/t/split-base-into-ghc-and-non-ghc-parts/14339/2 "2026-07-01T12:53:36Z")

</div>

The work I’ve been doing with Simon on known-keys [!15899](https://gitlab.haskell.org/ghc/ghc/-/merge_requests/15899) will make it possible to move a lot of code from `ghc-internal` back into `base`. At which point, it’ll be normal code rather than re-exports. It doesn’t solve the whole thing, but it’s a good start!

---

<div class="post-metadata">

**Author:** ![simonpj](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/simonpj/32/890_2.png) [@simonpj](https://discourse.haskell.org/u/simonpj)\
**Post date:** [July 6, 2026, 3:19pm UTC](https://discourse.haskell.org/t/split-base-into-ghc-and-non-ghc-parts/14339/3 "2026-07-06T15:19:46Z")

</div>

To split `base` up into GHC-specific and GHC-independenty parts would be entirely possible.

But it depends on someone defining an API that is implementable by several compilers (notably both micro-hs and GHC), upon which `base` can depend and which can be implemented by each compiler separately.

You might wonder if that is precisely `ghc-internal`. But that’s not the case right now: `ghc-internal` is precisely what it says: internal to GHC and with no aspirations to be compiler independent.

Once someone defines a compiler-independent API on which `base` can depend (in a compiler-independent way) then we can see if it’s best addressed by splitting `base`, or by re-defining `ghc-internal` to meet that API.

In short: we have now removed all the _technical_ difficulties with defining `base` atop a compiler-independent API. What remains is the question of who will design this compiler-independent API. The way lies open!
