# Pre-GHC-Proposal: Instantiate backpack signatures when importing

**URL:** <https://discourse.haskell.org/t/pre-ghc-proposal-instantiate-backpack-signatures-when-importing/6739>\
**Category:** Uncategorized\
**Created:** [June 28, 2023, 7:30pm UTC](https://discourse.haskell.org/t/pre-ghc-proposal-instantiate-backpack-signatures-when-importing/6739 "2023-06-28T19:30:09Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![ChShersh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/chshersh/32/2551_2.png) [@ChShersh](https://discourse.haskell.org/u/ChShersh)\
**Post date:** [July 4, 2023, 10:32am UTC](https://discourse.haskell.org/t/pre-ghc-proposal-instantiate-backpack-signatures-when-importing/6739/21 "2023-07-04T10:32:22Z")

</div>

I remember this message by @mpickering about Backpack:

> [@Deprecating Language Features](http://discourse.haskell.org/t/deprecating-language-features/5582/21):
>
> From my perspective the two features which incur large maintenance burden on my day-to-day work are safe haskell and backpack. For each developer their list will be different, I mostly work on driver related code so regularly my work gets stalled on fixing an assumption or misimplementation in the backpack code. This does lead to frustration but also a low level of confidence that the backpack implementation is robust for serious use.

In my understanding, if a feature is barely used but causes major pain for GHC developers, it should be ripped off.

Haskell doesn’t need a kitchen-sink of all possible features. Haskell needs a good Product Manager.

---

_[View the full topic](https://discourse.haskell.org/t/pre-ghc-proposal-instantiate-backpack-signatures-when-importing/6739)._