Re: Patch/feature proposal: Source plugins

2013-07-30 Thread Thomas Schilling
From: Edsko de Vries [mailto:edskodevr...@gmail.com] Sent: 08 July 2013 18:02 To: Simon Peyton-Jones Cc: Luite Stegeman; Thomas Schilling; ghc-devs@haskell.org; Nicolas Frisby Subject: Re: Patch/feature proposal: Source plugins Ok, sorry all for the delay. Attached is a frontend

Re: Patch/feature proposal: Source plugins

2013-07-25 Thread Edsko de Vries
. (And I’m rushing towards the POPL deadline anyway!) Simon From: Edsko de Vries [mailto:edskodevr...@gmail.com] Sent: 08 July 2013 18:02 To: Simon Peyton-Jones Cc: Luite Stegeman; Thomas Schilling; ghc-devs@haskell.org; Nicolas Frisby Subject: Re: Patch/feature proposal: Source plugins

Re: Patch/feature proposal: Source plugins

2013-07-08 Thread Edsko de Vries
@haskell.org *Subject:* Re: Patch/feature proposal: Source plugins ** ** Hi Luite, ** ** I was fully planning on a first version of the patch yesterday, but so far my efforts were thwarted by annoying problems with dynamic libraries (not -- directly -- related to the patch at all

Re: Patch/feature proposal: Source plugins

2013-07-08 Thread Austin Seipp
; Thomas Schilling; ghc-devs@haskell.org *Subject:* Re: Patch/feature proposal: Source plugins ** ** Hi Luite, ** ** I was fully planning on a first version of the patch yesterday, but so far my efforts were thwarted by annoying problems with dynamic libraries (not -- directly

RE: Patch/feature proposal: Source plugins

2013-06-28 Thread Simon Peyton-Jones
through it! No hurry, just when you are ready. Simon From: Edsko de Vries [mailto:edskodevr...@gmail.com] Sent: 26 June 2013 09:21 To: Luite Stegeman Cc: Simon Peyton-Jones; Thomas Schilling; ghc-devs@haskell.org Subject: Re: Patch/feature proposal: Source plugins Hi Luite, I was fully planning

Re: Patch/feature proposal: Source plugins

2013-06-26 Thread Luite Stegeman
-devs@haskell.org | Subject: Re: Patch/feature proposal: Source plugins | | On 5 June 2013 13:51, Edsko de Vries edskodevr...@gmail.com wrote: | It is a little bit messy mostly because parts of the AST get lost | along the | way: quasi-quotes in the renamer, data type declarations and other

Re: Patch/feature proposal: Source plugins

2013-06-26 Thread Edsko de Vries
| To: Edsko de Vries | Cc: ghc-devs@haskell.org | Subject: Re: Patch/feature proposal: Source plugins | | On 5 June 2013 13:51, Edsko de Vries edskodevr...@gmail.com wrote: | It is a little bit messy mostly because parts of the AST get lost | along the | way: quasi-quotes in the renamer, data

Re: Patch/feature proposal: Source plugins

2013-06-26 Thread Thomas Schilling
the GHC API. Simon | -Original Message- | From: ghc-devs-boun...@haskell.org [mailto:ghc-devs-boun...@haskell.org] | On Behalf Of Thomas Schilling | Sent: 11 June 2013 12:53 | To: Edsko de Vries | Cc: ghc-devs@haskell.org | Subject: Re: Patch/feature proposal: Source plugins | | On 5

Re: Patch/feature proposal: Source plugins

2013-06-11 Thread Luite Stegeman
Sounds good, but for some reason we have HscAsm as a target at the moment in GHCJS, and set it to HscNothing only after typechecking. I forgot why, might have something to do with TH. Do you have an implementation of this patch that i can test it with (even if it's not the final API or really

Re: Patch/feature proposal: Source plugins

2013-06-11 Thread Thomas Schilling
On 5 June 2013 13:51, Edsko de Vries edskodevr...@gmail.com wrote: It is a little bit messy mostly because parts of the AST get lost along the way: quasi-quotes in the renamer, data type declarations and other things during type checking. A more ideal way, but also more time consuming, would

RE: Patch/feature proposal: Source plugins

2013-06-11 Thread Simon Peyton-Jones
de Vries | Cc: ghc-devs@haskell.org | Subject: Re: Patch/feature proposal: Source plugins | | On 5 June 2013 13:51, Edsko de Vries edskodevr...@gmail.com wrote: | It is a little bit messy mostly because parts of the AST get lost | along the | way: quasi-quotes in the renamer, data type

Re: Patch/feature proposal: Source plugins

2013-06-07 Thread Luite Stegeman
I'd also be very happy with some plugin interface that allows us to use more GhcMake functionality from the GHC API. For GHCJS we would want to run our own (STG - JavaScript) code generator on sources that need to be recompiled instead of letting GHC run its pipeline. Do you think that's possible

Re: Patch/feature proposal: Source plugins

2013-06-06 Thread Simon Marlow
+1. I don't have any comments on the technical issues I'm afraid, but the more ways we can extend GHC without having to change it directly, the better. Cheers, Simon On 05/06/13 12:51, Edsko de Vries wrote: Sorry for the earlier mishap, here's the full email. Hi all, The plugin

Patch/feature proposal: Source plugins

2013-06-05 Thread Edsko de Vries
Hi all, The plugin mechanism gives access to the program in Core; this suffices for many but not quite all purposes. Tools that need access to the original AST can call typecheckModule directly, but of course this requires using the GHC API directly. Moreover, even when using the GHC API directly

Re: Patch/feature proposal: Source plugins

2013-06-05 Thread Edsko de Vries
Uh. I'm sorry, I don't know why that email got sent, I was still writing it. Please ignore it for now, will send the full version later :) On Wed, Jun 5, 2013 at 12:14 PM, Edsko de Vries edskodevr...@gmail.comwrote: Hi all, The plugin mechanism gives access to the program in Core; this

Patch/feature proposal: Source plugins

2013-06-05 Thread Edsko de Vries
Sorry for the earlier mishap, here's the full email. Hi all, The plugin mechanism gives access to the program in Core; this suffices for many but not quite all purposes. Tools that need access to the original AST can call typecheckModule directly, but of course this requires using the GHC API