Mike Pilgrem

With #182 now fixed: @Bodigrim, the original intent was the user would have tested `stdin` themselves, because they would want to do that only once, not every time they used...

Related issues/pull requests: * #124 * #140 (by @Bodigrim !)

@jeltsch, your original plan (#185, now overtaken by #187) was to use the `Win32` package's: ~~~haskell withHandleToHANDLE :: Handle -> (HANDLE -> IO a) -> IO a ~~~ The `withHandleToHANDLE`...

I looked at the packages identified by @TeofilC. My notes are in the table below. 'Likely imported qualified' indicates that the exporting module exports a lot of functions with names...

@meooow25, putting aside Haddock documentation for the moment, does this 'work' from that perspective? (EDIT: I realised my original version would end up with circular module dependencies) ~~~haskell import GHC.Internal.Data.List.NonEmpty...

@hasufell, I have not - but I was waiting for the discussion of alternatives to settle. I don't have experience myself in 'tweaking for space/time performance'; I'm usually in camp...

@hasufell, I'll have a go at an implementation - but it may be a little while hence, as there are some Stack things that is occupying me at present.

Thanks! Genuinely not forgotten, but a question of limited bandwidth and having to prioritise various things.

I arrived here via: * #4506 The [current documentation](https://github.com/haskell/haskell-language-server/blob/master/plugins/hls-eval-plugin/README.md) for `hls-eval-plugin` states: > IO expressions can also be evaluated but their output to stdout/stderr is NOT captured: > > `>>>...

@mpickering, on your question: > Is there a reason you move the documentation into `base-4.11-` rather than `base-4.11`? It is the other way around, as follows: * Stack uses Cabal...