# Could GHC remove old extensions?

**URL:** <https://discourse.haskell.org/t/could-ghc-remove-old-extensions/4416>\
**Category:** Uncategorized\
**Created:** [April 22, 2022, 7:22am UTC](https://discourse.haskell.org/t/could-ghc-remove-old-extensions/4416 "2022-04-22T07:22:08Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![atravers](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@atravers](https://discourse.haskell.org/u/atravers)\
**Post date:** [April 23, 2022, 9:03pm UTC](https://discourse.haskell.org/t/could-ghc-remove-old-extensions/4416/28 "2022-04-23T21:03:33Z")

</div>

Does it matter? We’re _all_ going to have our own opinions on what [_now_] are _“the extensions without which it is impossible to code”_, and they will change as the Haskell extend-a-thon continues. I think our new ED said it best, albeit in a somewhat-different context:

> [@Reconsider Slack for HF?](http://discourse.haskell.org/t/reconsider-slack-for-hf/4230/37):
>
> Meta-work spent figuring out how to do our work is important, but there’s definitely diminishing returns as more is done, and I worry that opening this can of worms right now will mean not getting other things done.

But if you really, **_really_** still want to discuss this, I humbly suggest starting a new thread…

---

_[View the full topic](https://discourse.haskell.org/t/could-ghc-remove-old-extensions/4416)._
