I admit I can’t judge the impact of this proposal without investing more time than I can currently spare, but I got to read it completely and it seems reasonable. +1 Best, Malte On 2026-04-20 17:00, Sebastian Graf wrote:
Right, I didn't mean to pressure anyone because we still have 4-5 weeks to gather votes. Just wanted to leave a friendly nudge after half time to get it to the top of everybody's inbox.
Thanks for the detailed review and vote, Simon.
Simon Peyton Jones <[1]simon.peytonjones@gmail.com> schrieb am Mo., 20. Apr. 2026, 00:40:
This proposal has been under discussion for nearly 2 weeks. So far, the tally is +3 votes in favour.
Right. Every member of the committee owes Sebastian a vote.
I had trouble understanding the proposal, so after I did my homework I [2]wrote a summary here. you may find that summary helpful in reviewing the proposal.
I vote yes.
Simon
On Sun, 19 Apr 2026 at 14:59, Sebastian Graf <[3]sgraf1337@gmail.com> wrote:
This proposal has been under discussion for nearly 2 weeks. So far, the tally is +3 votes in favour.
Am Di., 14. Apr. 2026 um 20:19 Uhr schrieb Jeff Young <[4]jmy6342@gmail.com>:
I believe this would be a net benefit to the whole ecosystem similar to the re-installable base work. Although I am not a heavy user of template Haskell its a +1 from me.
- Jeff
On Tue, Apr 14, 2026 at 4:50 AM Simon Marlow <[5]marlowsd@gmail.com> wrote:
I haven't read the whole proposal, but based on Sebastian's summary it seems like a reasonable thing to do. +1 from me.
Simon
On Mon, 6 Apr 2026 at 19:11, Sebastian Graf <[6]sgraf1337@gmail.com> wrote:
Dear committee,
Teo proposes to hide the implementation of the Q monad. This allows an internal only interface to be split out of Quasi. This enables the internal interface to evolve independently of Quasi, the external interface. This small change has a practically important benefit: adding a new function to Q (a seemingly minor change) no longer forces a major version bump of GHC to cause a major version bump of template-haskell that will transitively ripple through the whole ecosystem. I highly recommend we accept the proposal.
Sebastian
Am Di., 10. März 2026 um 10:55 Uhr schrieb Simon Marlow <[7]marlowsd@gmail.com>:
Teo Camarasu submitted proposal #700: Abstract Q to the committee for review.
[8]https://github.com/ghc-proposals/ghc-proposals/pull/700
I'd like to nominate Sebastian Graf as the shepherd.
Please guide us to a conclusion as outlined in [9]https://github.com/ghc-proposals/ghc-proposals/blob/master/README.rs t#committee-process-for-responding-to-a-proposal. If possible, please aim to make a recommendation by 24 March 2026.
Cheers Simon
_______________________________________________ ghc-steering-committee mailing list -- [10]ghc-steering-committee@haskell.org To unsubscribe send an email to [11]ghc-steering-committee-leave@haskell.org
_______________________________________________ ghc-steering-committee mailing list -- [12]ghc-steering-committee@haskell.org To unsubscribe send an email to [13]ghc-steering-committee-leave@haskell.org
_______________________________________________ ghc-steering-committee mailing list -- [14]ghc-steering-committee@haskell.org To unsubscribe send an email to [15]ghc-steering-committee-leave@haskell.org
_______________________________________________ ghc-steering-committee mailing list -- [16]ghc-steering-committee@haskell.org To unsubscribe send an email to [17]ghc-steering-committee-leave@haskell.org
References
1. mailto:simon.peytonjones@gmail.com 2. https://github.com/ghc-proposals/ghc-proposals/pull/700#issuecomment-4276986... 3. mailto:sgraf1337@gmail.com 4. mailto:jmy6342@gmail.com 5. mailto:marlowsd@gmail.com 6. mailto:sgraf1337@gmail.com 7. mailto:marlowsd@gmail.com 8. https://github.com/ghc-proposals/ghc-proposals/pull/700 9. https://github.com/ghc-proposals/ghc-proposals/blob/master/README.rst#commit... 10. mailto:ghc-steering-committee@haskell.org 11. mailto:ghc-steering-committee-leave@haskell.org 12. mailto:ghc-steering-committee@haskell.org 13. mailto:ghc-steering-committee-leave@haskell.org 14. mailto:ghc-steering-committee@haskell.org 15. mailto:ghc-steering-committee-leave@haskell.org 16. mailto:ghc-steering-committee@haskell.org 17. mailto:ghc-steering-committee-leave@haskell.org
_______________________________________________ ghc-steering-committee mailing list -- ghc-steering-committee@haskell.org To unsubscribe send an email to ghc-steering-committee-leave@haskell.org