Re: New Proposal: EasyMacros

[Richard Eisenberg]

Eek. Just realized that this went unanswered! Sorry!

Yes, a good next step is to email the Haskell-cafe list or to post on 
reddit.com/r/haskell. For the wiki page, I meant at the GHC developers' wiki, 
here: https://ghc.haskell.org/trac/ghc   But it might be best to get feedback 
first.

Richard

On May 19, 2016, at 5:20 AM, Anton Felix Lorenzen  wrote:

> I am glad you like the idea. I fully understand
> that it should be an extension first, I simply followed the 
> https://prime.haskell.org/wiki/Process
> 
> I am think I am not able to make a prime wiki page
> (at least I wasn't able to find a button for this).
> 
> Should I create a ghc wiki page?
> Email the Haskell-cafe list?
> 
> This is my first proposal and I m a bit lost here.
> 
> Thanks,
> Anton
> ___
> Haskell-prime mailing list
> Haskell-prime@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: Limber separators

[Alexander Berntsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 01/06/16 08:44, Herbert Valerio Riedel wrote:
> Well, I'd really like to see the grammar relaxed to allow for redundant
> leading separators so I could finally use my personal ideal
> diff-friendly style:
> 
>  something = [
>  , one
>  , thirteen
>  , two
>  , three
>  ]
If your ideal style uses every entry on one line regardless of how
short it is (in terms of character count), then surely simply 'ENTRY\n'
is better than ', ENTRY\n'? At least my preference in that case would be
no comma, or a trailing comma.
- -- 
Alexander
alexan...@plaimi.net
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXTq2NAAoJENQqWdRUGk8BZJMQAL5CGwQyVUJJP/oMUw7DpnI2
gXb/3uYF+Od6GAKLHZnPB4G2+fq7xXvINENki2T6u0/Va4FeQ/xTLrccR7j3o++1
c4LtxctUjpEz321Hi/v4Zq3JZL5XY6z39dZwUx0cMcCmUXk1+aVzmQGh1S4Y+/3E
ICHyAOESUB6vlMeL492qVGtD6drkstuQaDTKn/kry/jTgnAabcIa9hJ5EWj4DMFW
jTcpkDD8kLFTPlKN+ky8bN02RmMVkC8jZe5n1+S4WhWVK7Fixsib5nE5qaYl73Wq
FCFf2b8FKkoCyAMTfJmdZt2yXgl30+/DAJa60E7I40uh98Ak1uH1V02cpOOVt3FU
dgH1TWP/TP36VZ+HpJ85vdrbdioG5aQar4aeFVosd6vbIQNhiCKjcfR4aLo6C1Bg
zfORQtpzqq11M6SHTZG91L4+Ti/y4vfFE/qnY1YhP5dpTblT7TJRP/s4eQwXnfYs
GmhCOeev43P6mNL9TXyz4OkLzxrgdEzYWgdlGn88gg8dHIj5+BOxJNw9uJgb4iRq
ovz+efoGGN3lk3prNeD6VO7BZ6WRu3mi7JJcX2nmjyfOGK2tQE9eYuFS/oevkJwE
zFI7RAwi/UecN9jJ1do+zq/DBjQo2bRJnlswhwAdLxqhyyhxNuMvQdklibhlWsrZ
Irj2614mavqB67f3Os7k
=ojRm
-END PGP SIGNATURE-
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: Limber separators

[Herbert Valerio Riedel]

On 2016-05-31 at 15:42:14 +0200, Antonio Nikishaev wrote:

[...]

> Personally I don't need this extension per se since I don't care about one 
> excess diff line.
> What I do care about however, is the horrendous style people invented to 
> avoid “the diff problem”.
> As an example
>
> something = [ foo
> , bar
> , baz
> ]

I'm not sure this style was invented to address the diff-problem, as it
actually doesn't solve the problem at all; it only shifts the problem
from the last entry to the first entry in the enumeration.

Moreover, why do you call this a "horrendous" style?

I actually see benefits for trailing separators as you avoid the
separator-alignment problem you'd have with trailing separators:

You either have to use a ragged alignment (and in this case the `,`s are
IMHO hard to see as they're visually attached to their entries; one can
add a whitespace before the `,` though)

 something = [
 one,
 thirteen,
 two,
 three
 ]

or if you align the `,`s on the same column to make move separators
visually out of the way, i.e.

 something = [
 one  ,
 thirteen ,
 two  ,
 three
 ]

you may run into a worse diff-problem, once you add an entry that is
longer and would require to realign all `,`s.

That's why I personally consider the "horrendous" style (and I even
catch myself sometimes using this in non-Haskell), i.e.

 something =
 [ one
 , thirteen
 , two
 , three
 ]

to have quit a few benefits in its own right. And while I don't *need*
this extension either, I've been tempted to implement such an extension
myself every now and then when I refactor code and fail to move the `,`s
around, resulting in an at least one additional edit-save-recompile
cycle.

> So I’d really like to see this extension, even if only to conquer the
> aforementioned style.

:-)

Well, I'd really like to see the grammar relaxed to allow for redundant
leading separators so I could finally use my personal ideal
diff-friendly style:

 something = [
 , one
 , thirteen
 , two
 , three
 ]
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime

Re: Infrastructure status?

[M Farkas-Dyck]

On 31/05/2016, Herbert Valerio Riedel  wrote:
> I'd rather suggest to have 2 Git repos, to keep the concerns separate.
> And I think we can just start out with such a 2nd GitHub repo and
> make the process up as we go. At this point we should just get moving, as I
> sense many of you want to finally start writing up proposals!
>
> If this turns out to be a bad idea, we can just call it an instructive
> failed experiment, and move the content into some other form.

+1 all this.

> If there's no objections, I suggest we create a
>  repository with a similiar basic
> structure to  and see how far we get
> with that...

So will we all become members of the Haskell organization on GitHub?
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime