News for hackers. Stuff that matters.
Re:Haskell ArgumentDo Proposal by akhilcacharya on Monday July 04, 2016 @10:14PM (#12034037)
This would be absolutely amazing actually.
Re:Haskell ArgumentDo Proposal by platz on Tuesday July 05, 2016 @12:29AM (#12034403)
Wait till you see a rust-style datatype polymorphic over 4 parameters, and use that type over and over again. Haskell syntax may not make much sense coming from algol-inspired syntax, but to express its patterns it makes sense otherwise you end up with scala type lambda madness.

Both purescript and agda have this

Re:Haskell ArgumentDo Proposal by cfallin on Tuesday July 05, 2016 @02:09PM (#12038313)
I'm curious, what sorts of issues arise with complex types that Haskell-like syntax handles better? (Genuinely curious here -- I've written a little Haskell but am by no means an expert...)

IMHO a Rust-style type `Option<HashMap<String, Vec<u32>>>` is a little noiser than the Haskell-style type `Maybe (Map String [Int])`, but not fatally so. Maybe there are much worse cases though?

Re:Haskell ArgumentDo Proposal by ryani on Saturday July 09, 2016 @12:55AM (#12060161)
The big one is `->`; all the 'template argument'-inspired syntaxes for this are terrible. Once you realize you want operators (and polymorphic operators, at that!) in your types, the `<u32>`syntax falls apart.

I am not a fan of C#'s `Func<a,b>` at all.