Hi Simon, I'm happy to take this on. Through `singletons`, I am a heavy TH user and know that end of GHC well.
The one caveat I offer is that I vastly prefer to chunk up similar bits of work, and generally intend to let TH tickets languish until I sweep them all up, somewhere near the planned feature freeze. The plus side of this approach is that it gives oodles of time for new contributors to GHC to take a stab. As I've commented on Trac, TH is a fantastic way to introduce yourself to GHC hacking. Small enhancements to TH generally involve only a few files and have a predictable pattern. So, do get involved! I'll help along the way. In any case, I'll continue to monitor TH's overall evolution. Richard On Jun 26, 2015, at 3:55 AM, Simon Peyton Jones <[email protected]> wrote: > Friends > > I’m looking for someone, or a small group, to act as a Supreme Being for > Template Haskell. Might you be willing? > > There is a steady trickle of bug reports / feature requests relating to > Template Haskell, which I find that I simply don’t have the time to pay > proper attention to. Here is a recent example > http://ghc.haskell.org/trac/ghc/ticket/10572. But if no one pays attention, > they languish. > > None of them is very hard, but all require a little careful thought. What > should the Template Haskell API be like? What semantics do we want? > > My hope is that if someone, or a small group, felt mandated to push TH > forward, then we might make some progress. At the moment I have the uneasy > feeling that while everyone can make suggestions, it’s all waiting for SPJ to > decide something, and SPJ is not paying enough attention. I don’t want to be > a bottleneck. Moreover, since I’m not a heavy-duty TH user, I’m poorly > placed to make design choices. > > The reason I’m optimistic is because the steady trickle tells me that TH is > in fact highly valued and widely used. So perhaps among that group there are > some people who would be willing to debate alternative designs, make choices, > and implement them. > > I would be more than willing to act as consultant, both on design and > implementation. > > GHC absolutely relies on its community. Please consider making an offer to > help. Thanks! > > Simon > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
