Hi all,
Haskell-cafe is mirrored on Google Groups at
https://groups.google.com/forum/#!forum/haskell-cafe, as far as I can
tell. That enables anybody to join that ML and participate in existing
discussions. Would such mirroring be an option here too?
Cheers,
--
Paolo G. Giarrusso - Ph.D. Student,
Replying to
https://mail.haskell.org/pipermail/haskell-community/2016-August/000127.html
(I can't reply properly otherwise as I just subscribed):
> > 2) This really just boils down to the political gridlock between HP and
> > Stack. Unless the actual parties involved in that gridlock can hammer o
On 29 August 2016 at 17:39, Kosyrev Serge wrote:
> Gershom B writes:
>>> I might understand the concern about archiving, but haskell-cafe
>>> solves that. And "the committee can't be expected to follow
>>> discussions" and "is empowered to act" does sound like "the committee
>>> can't be expected
On 29 August 2016 at 17:21, Gershom B wrote:
> On August 29, 2016 at 11:15:19 AM, Paolo Giarrusso
> (paolo.giarru...@uni-tuebingen.de) wrote:
>
>> If the poll was announced there, there would still be extra friction.
>> But IIUC only the mailing list was announced there.
On 29 August 2016 at 17:29, Nicolas Wu wrote:
> Hello,
>
> I think having multiple options is confusing to beginners, and so I'd like
> to see a single download option on the download page.
>
> For me it's important that we have a way for beginners to use tools like ghc
> and ghci on the command l
On 30 August 2016 at 15:56, Steven J. Syrek wrote:
> alias ghci="stack ghci"
>
> ?
stack ghci translates to cabal repl which interprets your whole
project. No biggie on small projects, but annoying on big ones.
But the correct alias is closer to
alias ghci='stack exec -- ghci'
Though you *could
On 2 September 2016 at 01:48, Patrick Pelletier
wrote:
> On 9/1/16 2:12 PM, Gershom B wrote:
>>
>> We've had a productive discussion on this list, I think. But as many
>> probably know, not all the discussions over this have been so
>> positive.
> I am really happy about the positive, conciliator
On Tuesday, September 13, 2016 at 9:47:20 PM UTC+2, Richard Eisenberg wrote:
>
> Thanks, many, for explaining better ways to interact directly with GHC
> after using a `stack setup`. Perhaps, then, all that’s stopping someone
> like me from liking the ease of `stack setup` is a little missing P
On Tuesday, September 13, 2016 at 8:58:53 PM UTC+2, Richard Eisenberg wrote:
>
> I’ve watched the recent back-and-forth about stack with quite a bit of
> interest (as many of us have). The discussion inspired me to take another
> look at stack. Here are the results of that foray.
>
> First, a dis
e the work and not asking anybody—I've just been busy.
Right now I have to modify the PATH every time I use GHC 7.8.4 because I
needed to customize the build (I'm on OS X 10.11), but I still want GHC 8
by default.
> On Tue, Sep 13, 2016 at 3:01 PM, Paolo Giarrusso > wrote
(Resending from right address)
We're talking about *three* options:
1. syntax for pure Haskell values, which I'll call HSON (Haskell
jSON). That's just an alternative to YAML/TOML/... That would need
extensions to allow omitting optional fields entirely.
2. a pure Haskell embedded domain-specific
On 16 September 2016 at 12:13, Patrick Pelletier
wrote:
> On 9/16/16 2:36 AM, Paolo Giarrusso wrote:
>>
>> (Resending from right address)
>>
>> We're talking about *three* options:
>> 1. syntax for pure Haskell values, which I'll call HSON (Haskell
&
fig language. Haskell will make a much better choice for such use
> cases. Pure declarative is a pain for such use cases.
> On 16 September 2016 at 16:08, Paolo Giarrusso
> wrote:
>>
>> On 16 September 2016 at 12:13, Patrick Pelletier
>> wrote:
>> > On 9/16/16 2:36 A
We're talking about *three* options:
1. syntax for pure Haskell values, which I'll call HSON (Haskell
jSON). That's just an alternative to YAML/TOML/... That would need
extensions to allow omitting optional fields entirely.
2. a pure Haskell embedded domain-specific language (EDSL) that simply
gene
Rust's code of conduct (and the conduct of leaders) have been very
successful at creating a welcoming community. However, those rules were
there from the start.
What's crucial is that a code of conduct is really agreed upon by a
community and its elders. So thanks to Simon Peyton Jones for startin
15 matches
Mail list logo
