From adam at well-typed.com Mon Jun 16 07:17:00 2025 From: adam at well-typed.com (Adam Gundry) Date: Mon, 16 Jun 2025 08:17:00 +0100 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell Message-ID: Dear Committee, Teo Camarasu proposes to split out smaller, more coherent packages with more stable interfaces from the template-haskell package: https://github.com/ghc-proposals/ghc-proposals/pull/696 https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst I'd like to nominate Sebastian as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Cheers, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England From sgraf1337 at gmail.com Mon Jun 23 07:55:19 2025 From: sgraf1337 at gmail.com (Sebastian Graf) Date: Mon, 23 Jun 2025 09:55:19 +0200 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: Dear Committee, With their proposal, Teo wants to reduce the maintenance cost for packages (such as `containers`) that depend on `template-haskell` only for comparatively stable APIs (`Lift`, quasiquoting), by carving out separate packages for these stable APIs. These so-called "type (A) clients" constitute a considerable share of all clients of `template-haskell`. It is a well-written proposal outlining a simple solution with a great cost/benefit ratio. I recommend we accept it. Cheers, Sebastian Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via ghc-steering-committee : > Dear Committee, > > Teo Camarasu proposes to split out smaller, more coherent packages with > more stable interfaces from the template-haskell package: > > https://github.com/ghc-proposals/ghc-proposals/pull/696 > > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > I'd like to nominate Sebastian as the shepherd. > > Please guide us to a conclusion as outlined in > https://github.com/ghc-proposals/ghc-proposals#committee-process > > Cheers, > > Adam > > > -- > Adam Gundry, Haskell Consultant > Well-Typed LLP, https://www.well-typed.com/ > > Registered in England & Wales, OC335890 > 27 Old Gloucester Street, London WC1N 3AX, England > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpg at mpg.is Mon Jun 23 10:06:15 2025 From: mpg at mpg.is (=?UTF-8?Q?Matth=C3=ADas_P=C3=A1ll_Gissurarson?=) Date: Mon, 23 Jun 2025 10:06:15 +0000 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: I think it's reasonable and well thought out. I vote accept. On Mon, 23 Jun 2025 at 07:55, Sebastian Graf via ghc-steering-committee < ghc-steering-committee at haskell.org> wrote: > Dear Committee, > > With their proposal, Teo wants to reduce the maintenance cost for packages > (such as `containers`) that depend on `template-haskell` only for > comparatively stable APIs (`Lift`, quasiquoting), by carving out separate > packages for these stable APIs. > These so-called "type (A) clients" constitute a considerable share of all > clients of `template-haskell`. It is a well-written proposal outlining a > simple solution with a great cost/benefit ratio. > I recommend we accept it. > > Cheers, > Sebastian > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > ghc-steering-committee : > >> Dear Committee, >> >> Teo Camarasu proposes to split out smaller, more coherent packages with >> more stable interfaces from the template-haskell package: >> >> https://github.com/ghc-proposals/ghc-proposals/pull/696 >> >> https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst >> >> I'd like to nominate Sebastian as the shepherd. >> >> Please guide us to a conclusion as outlined in >> https://github.com/ghc-proposals/ghc-proposals#committee-process >> >> Cheers, >> >> Adam >> >> >> -- >> Adam Gundry, Haskell Consultant >> Well-Typed LLP, https://www.well-typed.com/ >> >> Registered in England & Wales, OC335890 >> 27 Old Gloucester Street, London WC1N 3AX, England >> _______________________________________________ >> ghc-steering-committee mailing list >> ghc-steering-committee at haskell.org >> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee >> > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -- -- Matthías Páll Gissurarson -------------- next part -------------- An HTML attachment was scrubbed... URL: From erikd at mega-nerd.com Mon Jun 23 10:36:57 2025 From: erikd at mega-nerd.com (Erik de Castro Lopo) Date: Mon, 23 Jun 2025 20:36:57 +1000 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: <20250623203657.1885b81f938d6c1c64d27693@mega-nerd.com> I read through the GH issues and the proposal when it was last posted to this list. TH is somewhat problematic in a number of areas but this proposal is a good start at addressing that. I vote accept. Erik Sebastian Graf via ghc-steering-committee wrote: > Dear Committee, > > With their proposal, Teo wants to reduce the maintenance cost for packages > (such as `containers`) that depend on `template-haskell` only for > comparatively stable APIs (`Lift`, quasiquoting), by carving out separate > packages for these stable APIs. > These so-called "type (A) clients" constitute a considerable share of all > clients of `template-haskell`. It is a well-written proposal outlining a > simple solution with a great cost/benefit ratio. > I recommend we accept it. > > Cheers, > Sebastian > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > ghc-steering-committee : > > > Dear Committee, > > > > Teo Camarasu proposes to split out smaller, more coherent packages with > > more stable interfaces from the template-haskell package: > > > > https://github.com/ghc-proposals/ghc-proposals/pull/696 > > > > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > > > I'd like to nominate Sebastian as the shepherd. > > > > Please guide us to a conclusion as outlined in > > https://github.com/ghc-proposals/ghc-proposals#committee-process > > > > Cheers, > > > > Adam > > > > > > -- > > Adam Gundry, Haskell Consultant > > Well-Typed LLP, https://www.well-typed.com/ > > > > Registered in England & Wales, OC335890 > > 27 Old Gloucester Street, London WC1N 3AX, England > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/ From malte.ott at maralorn.de Mon Jun 23 13:11:54 2025 From: malte.ott at maralorn.de (Malte Ott) Date: Mon, 23 Jun 2025 15:11:54 +0200 Subject: [ghc-steering-committee] Please review #669: Initial categorization of language extensions In-Reply-To: <6581139a-1784-4ecd-81e4-13a7848d9d27@well-typed.com> References: <6581139a-1784-4ecd-81e4-13a7848d9d27@well-typed.com> Message-ID: Dear Committee, On 2024-10-29 19:45, Adam Gundry wrote: > Trevis Elser proposes a classification of (some) language extensions based > on previous work in proposal #601 establishing categories: > > https://github.com/ghc-proposals/ghc-proposals/pull/669 > > https://github.com/telser/ghc-proposals/blob/initial-extension-categorization/proposals/0000-extension-categorization.md (Note that additionally to adding the new proposal the PR also contains a small diff to the previous proposal #601.) This proposal rested for a while, but after some revisions at Zurihac I am recommending to accept this proposal. The proposal is the logical next step after the acceptance of #601. It’s not pretty to have a categorization but not use it and I think the classification is very helpful to guide users and us. In the proposal Trevis nominates 72 extensions as stable, 10 extensions as deprecated, 5 extensions as legacy, 8 extensions as experimental and 42 remain unclassified. This only affects documentation and our future decisions. Only observable change in GHC will be that deprecated extensions consistently get a warning via -Wdeprecated-flags. The intention is to basically just describe the status quo with the classification and defer all contentious extensions to be classified later. My general tendency is that we should err in the direction of marking extensions stable because at least for widely used extensions, even those where we are not very happy with the design, marking them experimental is like giving us a free pass to break our stability principle. Also marking an extension stable is not the same as "recommended" as it is perfectly fine for an extension to be stable but not part of a GHCXXXX language edition. Note that "For an extension to be classified as Stable it must be considered Stable when used in combination of all possible, non-mutually exclusive, extensions that are already Stable." I admit that I cannot judge this with certainty for all listed extensions. To be honest I learned e.g. of the existence of NoTraditionalRecordSyntax from reading the list. While I have been told that the categorization has been produced in close collaboration with GHC devs I ask everyone to keep this in mind when reviewing the list. Please review the overall proposal and the proposed categories. You can give your approval conditional on moving some extensions to "unclassified". Others and I have already done so, so from my point of view the list is good as is. Best, Malte From malte.ott at maralorn.de Mon Jun 23 13:39:33 2025 From: malte.ott at maralorn.de (Malte Ott) Date: Mon, 23 Jun 2025 15:39:33 +0200 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: I agree. I like this. On 2025-06-23 10:06, Matthías Páll Gissurarson via ghc-steering-committee wrote: > I think it's reasonable and well thought out. I vote accept. > > On Mon, 23 Jun 2025 at 07:55, Sebastian Graf via ghc-steering-committee > <[1]ghc-steering-committee at haskell.org> wrote: > > Dear Committee, > > With their proposal, Teo wants to reduce the maintenance cost for > packages (such as `containers`) that depend on `template-haskell` only > for comparatively stable APIs (`Lift`, quasiquoting), by carving out > separate packages for these stable APIs. > These so-called "type (A) clients" constitute a considerable share of > all clients of `template-haskell`. It is a well-written proposal > outlining a simple solution with a great cost/benefit ratio. > I recommend we accept it. > > Cheers, > Sebastian > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > ghc-steering-committee <[2]ghc-steering-committee at haskell.org>: > > Dear Committee, > > Teo Camarasu proposes to split out smaller, more coherent packages > with > more stable interfaces from the template-haskell package: > > [3]https://github.com/ghc-proposals/ghc-proposals/pull/696 > [4]https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-qua > siquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > I'd like to nominate Sebastian as the shepherd. > > Please guide us to a conclusion as outlined in > [5]https://github.com/ghc-proposals/ghc-proposals#committee-process > > Cheers, > > Adam > > -- > Adam Gundry, Haskell Consultant > Well-Typed LLP, [6]https://www.well-typed.com/ > > Registered in England & Wales, OC335890 > 27 Old Gloucester Street, London WC1N 3AX, England > _______________________________________________ > ghc-steering-committee mailing list > [7]ghc-steering-committee at haskell.org > [8]https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-co > mmittee > > _______________________________________________ > ghc-steering-committee mailing list > [9]ghc-steering-committee at haskell.org > [10]https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-c > ommittee > > -- > > -- [11]Matthías Páll Gissurarson > > References > > 1. mailto:ghc-steering-committee at haskell.org > 2. mailto:ghc-steering-committee at haskell.org > 3. https://github.com/ghc-proposals/ghc-proposals/pull/696 > 4. https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > 5. https://github.com/ghc-proposals/ghc-proposals#committee-process > 6. https://www.well-typed.com/ > 7. mailto:ghc-steering-committee at haskell.org > 8. https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > 9. mailto:ghc-steering-committee at haskell.org > 10. https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > 11. http://mpg.is/ > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From moritz.angermann at gmail.com Mon Jun 23 21:50:37 2025 From: moritz.angermann at gmail.com (Moritz Angermann) Date: Tue, 24 Jun 2025 06:50:37 +0900 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: While I’d rather see us burn TH outright to the ground, I’ve had some good discussions with Teo at ZuriHac as well and applaud his efforts to try to make the status quo at least somewhat better. I’m still afraid that any proliferation of TH is problematic, yet this is a pragmatic approach going into the right direction given the current situation. - moritz On Mon, Jun 23, 2025 at 10:39 PM Malte Ott via ghc-steering-committee < ghc-steering-committee at haskell.org> wrote: > I agree. I like this. > > On 2025-06-23 10:06, Matthías Páll Gissurarson via ghc-steering-committee > wrote: > > I think it's reasonable and well thought out. I vote accept. > > > > On Mon, 23 Jun 2025 at 07:55, Sebastian Graf via > ghc-steering-committee > > <[1]ghc-steering-committee at haskell.org> wrote: > > > > Dear Committee, > > > > With their proposal, Teo wants to reduce the maintenance cost for > > packages (such as `containers`) that depend on `template-haskell` only > > for comparatively stable APIs (`Lift`, quasiquoting), by carving out > > separate packages for these stable APIs. > > These so-called "type (A) clients" constitute a considerable share of > > all clients of `template-haskell`. It is a well-written proposal > > outlining a simple solution with a great cost/benefit ratio. > > I recommend we accept it. > > > > Cheers, > > Sebastian > > > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > > ghc-steering-committee <[2]ghc-steering-committee at haskell.org>: > > > > Dear Committee, > > > > Teo Camarasu proposes to split out smaller, more coherent packages > > with > > more stable interfaces from the template-haskell package: > > > > [3]https://github.com/ghc-proposals/ghc-proposals/pull/696 > > [4] > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-qua > > siquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > > > I'd like to nominate Sebastian as the shepherd. > > > > Please guide us to a conclusion as outlined in > > [5]https://github.com/ghc-proposals/ghc-proposals#committee-process > > > > Cheers, > > > > Adam > > > > -- > > Adam Gundry, Haskell Consultant > > Well-Typed LLP, [6]https://www.well-typed.com/ > > > > Registered in England & Wales, OC335890 > > 27 Old Gloucester Street, London WC1N 3AX, England > > _______________________________________________ > > ghc-steering-committee mailing list > > [7]ghc-steering-committee at haskell.org > > [8] > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-co > > mmittee > > > > _______________________________________________ > > ghc-steering-committee mailing list > > [9]ghc-steering-committee at haskell.org > > [10] > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-c > > ommittee > > > > -- > > > > -- [11]Matthías Páll Gissurarson > > > > References > > > > 1. mailto:ghc-steering-committee at haskell.org > > 2. mailto:ghc-steering-committee at haskell.org > > 3. https://github.com/ghc-proposals/ghc-proposals/pull/696 > > 4. > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > 5. https://github.com/ghc-proposals/ghc-proposals#committee-process > > 6. https://www.well-typed.com/ > > 7. mailto:ghc-steering-committee at haskell.org > > 8. > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > 9. mailto:ghc-steering-committee at haskell.org > > 10. > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > 11. http://mpg.is/ > > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.peytonjones at gmail.com Wed Jun 25 14:27:27 2025 From: simon.peytonjones at gmail.com (Simon Peyton Jones) Date: Wed, 25 Jun 2025 15:27:27 +0100 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: I'm in favour. Simon On Mon, 23 Jun 2025 at 08:55, Sebastian Graf via ghc-steering-committee < ghc-steering-committee at haskell.org> wrote: > Dear Committee, > > With their proposal, Teo wants to reduce the maintenance cost for packages > (such as `containers`) that depend on `template-haskell` only for > comparatively stable APIs (`Lift`, quasiquoting), by carving out separate > packages for these stable APIs. > These so-called "type (A) clients" constitute a considerable share of all > clients of `template-haskell`. It is a well-written proposal outlining a > simple solution with a great cost/benefit ratio. > I recommend we accept it. > > Cheers, > Sebastian > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > ghc-steering-committee : > >> Dear Committee, >> >> Teo Camarasu proposes to split out smaller, more coherent packages with >> more stable interfaces from the template-haskell package: >> >> https://github.com/ghc-proposals/ghc-proposals/pull/696 >> >> https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst >> >> I'd like to nominate Sebastian as the shepherd. >> >> Please guide us to a conclusion as outlined in >> https://github.com/ghc-proposals/ghc-proposals#committee-process >> >> Cheers, >> >> Adam >> >> >> -- >> Adam Gundry, Haskell Consultant >> Well-Typed LLP, https://www.well-typed.com/ >> >> Registered in England & Wales, OC335890 >> 27 Old Gloucester Street, London WC1N 3AX, England >> _______________________________________________ >> ghc-steering-committee mailing list >> ghc-steering-committee at haskell.org >> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee >> > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adam at well-typed.com Thu Jun 26 08:25:04 2025 From: adam at well-typed.com (Adam Gundry) Date: Thu, 26 Jun 2025 09:25:04 +0100 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: References: Message-ID: <62a93f67-d413-4232-9b1e-deb64048dad0@well-typed.com> I'm also in favour. I am suggesting some small naming changes, and I would point out one detail on which the committee may have opinions as to bikeshed colour, namely the module namespace to be used by the new packages. Teo proposes template-haskell-lift with module TemplateHaskell.Lift template-haskell-quasiquote with module TemplateHaskell.Quasiquoter and I suggest slightly tweaking the latter to template-haskell-quasiquoter with module TemplateHaskell.QuasiQuoter for consistency with the QuasiQuoter type name. In both cases, the module name is in a new TemplateHaskell module hierarchy, whereas the existing template-haskell package uses the Language.Haskell.TH module hierarchy. I think a renaming is in order, because it gives a clear distinction between the historic API of the old template-haskell package and the cleaned up APIs of the new packages. Personally I like the new names, but I wanted to check others are also happy with them? Cheers, Adam On 23/06/2025 08:55, Sebastian Graf wrote: > Dear Committee, > > With their proposal, Teo wants to reduce the maintenance cost for > packages (such as `containers`) that depend on `template-haskell` only > for comparatively stable APIs (`Lift`, quasiquoting), by carving out > separate packages for these stable APIs. > These so-called "type (A) clients" constitute a considerable share of > all clients of `template-haskell`. It is a well-written proposal > outlining a simple solution with a great cost/benefit ratio. > I recommend we accept it. > > Cheers, > Sebastian > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > ghc-steering-committee >: > > Dear Committee, > > Teo Camarasu proposes to split out smaller, more coherent packages with > more stable interfaces from the template-haskell package: > > https://github.com/ghc-proposals/ghc-proposals/pull/696 > > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > I'd like to nominate Sebastian as the shepherd. > > Please guide us to a conclusion as outlined in > https://github.com/ghc-proposals/ghc-proposals#committee-process > > > Cheers, > > Adam > -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England From sgraf1337 at gmail.com Mon Jun 30 08:27:04 2025 From: sgraf1337 at gmail.com (Sebastian Graf) Date: Mon, 30 Jun 2025 10:27:04 +0200 Subject: [ghc-steering-committee] Please review #696: Splitting out stable interfaces from template-haskell In-Reply-To: <62a93f67-d413-4232-9b1e-deb64048dad0@well-typed.com> References: <62a93f67-d413-4232-9b1e-deb64048dad0@well-typed.com> Message-ID: I think the renaming proposed by Adam is uncontroversial and I will include this revision when accepting the proposal. Am Do., 26. Juni 2025 um 10:25 Uhr schrieb Adam Gundry : > I'm also in favour. > > I am suggesting some small naming changes, and I would point out one > detail on which the committee may have opinions as to bikeshed colour, > namely the module namespace to be used by the new packages. Teo proposes > > template-haskell-lift with module TemplateHaskell.Lift > template-haskell-quasiquote with module TemplateHaskell.Quasiquoter > > and I suggest slightly tweaking the latter to > > template-haskell-quasiquoter with module TemplateHaskell.QuasiQuoter > > for consistency with the QuasiQuoter type name. > > In both cases, the module name is in a new TemplateHaskell module > hierarchy, whereas the existing template-haskell package uses the > Language.Haskell.TH module hierarchy. I think a renaming is in order, > because it gives a clear distinction between the historic API of the old > template-haskell package and the cleaned up APIs of the new packages. > Personally I like the new names, but I wanted to check others are also > happy with them? > > Cheers, > > Adam > > > > On 23/06/2025 08:55, Sebastian Graf wrote: > > Dear Committee, > > > > With their proposal, Teo wants to reduce the maintenance cost for > > packages (such as `containers`) that depend on `template-haskell` only > > for comparatively stable APIs (`Lift`, quasiquoting), by carving out > > separate packages for these stable APIs. > > These so-called "type (A) clients" constitute a considerable share of > > all clients of `template-haskell`. It is a well-written proposal > > outlining a simple solution with a great cost/benefit ratio. > > I recommend we accept it. > > > > Cheers, > > Sebastian > > > > Am Mo., 16. Juni 2025 um 09:17 Uhr schrieb Adam Gundry via > > ghc-steering-committee > >: > > > > Dear Committee, > > > > Teo Camarasu proposes to split out smaller, more coherent packages > with > > more stable interfaces from the template-haskell package: > > > > https://github.com/ghc-proposals/ghc-proposals/pull/696 > > > > > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > < > https://github.com/TeofilC/ghc-proposals/blob/wip/th-lift-and-quasiquote/proposals/0000-splitting-out-stable-interfaces-from-th.rst > > > > > > I'd like to nominate Sebastian as the shepherd. > > > > Please guide us to a conclusion as outlined in > > https://github.com/ghc-proposals/ghc-proposals#committee-process > > > > > > Cheers, > > > > Adam > > > > -- > Adam Gundry, Haskell Consultant > Well-Typed LLP, https://www.well-typed.com/ > > Registered in England & Wales, OC335890 > 27 Old Gloucester Street, London WC1N 3AX, England > > -------------- next part -------------- An HTML attachment was scrubbed... URL: