David Luposchainsky

Playing around with TSP solvers yielded no *significant* improvement over naive nearest-neighbour optimization when throwing computational power at the problem. I’m closing this as unnecessary or not worth the effort.

@gbaz Probably yes, but I think if the discussion is lively and altogether in favour of the proposal, we don’t need to appoint a shepherd to guide through it. The...

@gbaz On second thought, maybe it’s not so bad if we try out the shepherd thing on a smaller issue.

Added a note about the multiple argument shortcoming.

We do not allow trailing commas right now, do we? I don’t think that discussion has ever come to a conclusion. TupleSections is far older, and in my opinion more...

Adding the grammar elements is a good idea, and we should probably keep this in mind for further proposals. I’ll add it within the next days. @yav Shepherd? :-)

@yav Sorry for the late update, I added your grammar change suggestion

Wasn’t it the case that `MultiWayIf` _did not_ introduce a layout block that led to weird bugs? If I recall correctly, nested `if`s would have really awkward behaviour, resulting in...

[I think the Trac ticket I linked above gives quite a compelling example,](https://ghc.haskell.org/trac/ghc/ticket/4359#comment:90) > ``` > x = if | False -> if | False -> 1 > | False...

``` haskell f !x = ... ``` has different semantics when bang patterns are enabled than in current Haskell: it’s strict in `x`, or defines the infix `!` operator. I...