Re: Moving ArgumentsDo forward

2016-06-06 Thread Andrew Gibiansky
As the author of the proposal and extension, I'd like to clarify that the change was abandoned per se because of how controversial the change was. [0] [1] [2] This is not to say that we should not continue to discuss this change, but if we do so, make sure that you first read through the previous

Re: Remote GHCi

2015-11-19 Thread Andrew Gibiansky
answer is yes, we can support that more easily with remote > GHCi. I'll think about what API we can provide for it. > > Cheers, > Simon > > > On 18/11/2015 16:26, Andrew Gibiansky wrote: > >> Simon, >> >> I'd like to hear how we can support what IHask

Re: Remote GHCi

2015-11-18 Thread Andrew Gibiansky
Simon, I'd like to hear how we can support what IHaskell does with remote GHCi. One core functionality that we use dynCompileExpr for (not quite dynCompileExpr, but similar) is getting the standard output of code that is being run. Any time code is run, we 1. Create a unix pipe. 2. Set stdout to

Re: Remote GHCi

2015-11-17 Thread Andrew Gibiansky
Simon, As Sumit said, we use dynCompileExpr for core functionality of IHaskell. I am not really sure how the change you are proposing affects that, though. We use dynCompileExpr in several places for evaluation inside the interpreter context: 1. Evaluating a Haskell expression in the interpreter

Re: Proposal: Argument Do

2015-09-05 Thread Andrew Gibiansky
Thomas, Thanks for cleaning stuff up on the Newcomers page and others. I think all the things that were somewhat confusing before are now much clearer and less vague. -- Andrew On Sat, Sep 5, 2015 at 2:43 AM, Thomas Miedema wrote: > If you had used `BuildFlavour = stage2` as the Newcomers page

Proposal: Argument Do

2015-09-05 Thread Andrew Gibiansky
Trac: https://ghc.haskell.org/trac/ghc/ticket/10843 I would like the following to be valid Haskell code: main = when True do putStrLn "Hello!" Instead of requiring a dollar sign before the "do". This would parse as main = when True (do putStrLn "Hello!") Has this been tried before? It see

Re: Request for input on #7253: Top-level bindings in GHCI

2015-08-22 Thread Andrew Gibiansky
I would suggest treating "a = 1" as a declaration. This is what IHaskell does, and it seems more intuitive than hacky parsing it into a "let a = 1". The implementation should be easy using runDecls from InteractiveEval and parseDeclaration from Parser.y to do the actual parsing. -- Andrew On Sat,

Re: Building GHC API Documentation?

2014-07-15 Thread Andrew Gibiansky
g the command in the ./ghc subdirectory? > (Not the top directory -- it's probably ./ghc/ghc on your machine.) > > If you get that error on a clean checkout, you could perhaps post a bug > report. > > Richard > > On Jul 14, 2014, at 10:50 PM, Andrew Gibiansky &

Re: Building GHC API Documentation?

2014-07-14 Thread Andrew Gibiansky
Any suggestions? I'm still stuck on this, and don't really know what to try next. Andrew On Thu, Jul 10, 2014 at 9:36 PM, Andrew Gibiansky < andrew.gibian...@gmail.com> wrote: > Hello, > > I am trying to create my first patch, for #9294, where I want to export > s

Building GHC API Documentation?

2014-07-10 Thread Andrew Gibiansky
Hello, I am trying to create my first patch, for #9294, where I want to export some extra things from Parser along with a bit of documentation. However, I cannot figure out how to regenerate the documentation for the GHC API (not for the libraries). I tried running `make html stage=0 FAST=YES` in

Expose Other Parsers for GHC API

2014-05-30 Thread Andrew Gibiansky
hemselves are pretty opaque here. I think (1) and (3) are definitely a good idea, not so sure about (2) though IMHO it would be convenient for using the Parser. Would this make for an acceptable patch? Thoughts? -- Andrew Gibiansky ___ ghc-devs m

Re: Changing GHC Error Message Wrapping

2014-01-10 Thread Andrew Gibiansky
Thanks! On Fri, Jan 10, 2014 at 9:21 AM, Simon Peyton Jones wrote: > Crumbs. You are absolutely right. I’ll fix that. (It’s a relic from > when the flags weren’t available to the show functions.) > > > > Simon > > > > *From:* Andrew Gibiansky [mailto:andrew.gib

Re: Changing GHC Error Message Wrapping

2014-01-08 Thread Andrew Gibiansky
pprCols. It can’t: show :: a -> String! No command-line inputs. > > > > I suggest something more like > > > > doc sdoc = do { dflags <- getDynFlags; unqual <- getPrintUnqual; return > (showSDocForUser dflags unqual doc } > > > > Simon > > >

Re: Changing GHC Error Message Wrapping

2014-01-07 Thread Andrew Gibiansky
+ s2 string_txt (Pretty.PStr s1) s2 = unpackFS s1 ++ s2 string_txt (Pretty.LStr s1 _) s2 = unpackLitString s1 ++ s2 As far as I can tell, there is no simpler way, every function in `Pretty` except for `fullRender` just assumes a default of 100-char lines. -- Andrew On Tue, Jan 7, 2014 at 11:29 AM,

Re: Changing GHC Error Message Wrapping

2014-01-07 Thread Andrew Gibiansky
a bug - because this seems like buggy behaviour... Andrew On Tue, Jan 7, 2014 at 4:14 AM, Simon Peyton Jones wrote: > -dppr-cols=N changes the width of the output page; you could try a large > number there. There isn’t a setting meaning “infinity”, sadly. > > > >

Re: Changing GHC Error Message Wrapping

2014-01-06 Thread Andrew Gibiansky
better or worse. In general, should multi-line tuples be printed with many > elements per line, or just one? > > > > Simon > > > > *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Andrew > Gibiansky > *Sent:* 04 January 2014 17:30 > *To:*

Re: Changing GHC Error Message Wrapping

2014-01-04 Thread Andrew Gibiansky
Apologize for the broken image formatting. With the code I posted above, I get the following output: Couldn't match expected type `(GHC.Types.Int, GHC.Types.Int, GHC.Types.Int, t0,

Fwd: Changing GHC Error Message Wrapping

2014-01-03 Thread Andrew Gibiansky
Hello, I'd like to change how the error messages from GHC get wrapped. I am using the following code: flip gcatch handler $ do runStmt "let f (x, y, z, w, e, r, d , ax, b ,c,ex ,g ,h) = (x :: Int) + y + z" RunToCompletion runStmt "f (1, 2, 3)" RunToCompletion return () where