Re: Why not allow empty record updates?

2011-11-16 Thread Yitzchak Gale
I wrote: Yes. The translation of record updates given in the Report makes perfect sense for {}. It is only forbidden by n = 1, but no reason is given for that restriction. d wagner wrote: It doesn't make sense to me. The translation explodes a value into a case statement over its

RE: Why not allow empty record updates?

2011-11-16 Thread Simon Peyton-Jones
| Trouble is, what type does this have? |f x = x {} | | Malcolm Wallace wrote: | f :: a - a | | Ian Lynagh wrote: | That wouldn't help the original poster, as it is incompatible with | f :: Foo Clean - Foo Dirty There are several different things going on in this thread. 1.

Re: encoding and paths, again

2011-11-16 Thread Simon Marlow
On 16/11/2011 08:09, Ganesh Sittampalam wrote: On 14/11/2011 14:47, Simon Marlow wrote: (1) Does Win32 need similar additions? I can't spot any substantial changes to it for Max's PEP383, but I'm not sure if any lower-level library changes might have affected it. No - Win32 file paths cannot

Re: Way to expose BLACKHOLES through an API?

2011-11-16 Thread Duncan Coutts
On Tue, 2011-11-08 at 15:43 +, Simon Marlow wrote: Hmm, but there is something you could do. Suppose a thread could be in a mode in which instead of blocking on a BLACKHOLE it would just throw an asynchronous exception WouldBlock. Any computation in progress would be safely abandoned

Re: Way to expose BLACKHOLES through an API?

2011-11-16 Thread Jean-Marie Gaillourdet
Hi, On 16.11.2011, at 10:43, Duncan Coutts wrote: On Tue, 2011-11-08 at 15:43 +, Simon Marlow wrote: Hmm, but there is something you could do. Suppose a thread could be in a mode in which instead of blocking on a BLACKHOLE it would just throw an asynchronous exception WouldBlock.

Re: Way to expose BLACKHOLES through an API?

2011-11-16 Thread Simon Marlow
On 16/11/2011 10:20, Jean-Marie Gaillourdet wrote: Hi, On 16.11.2011, at 10:43, Duncan Coutts wrote: On Tue, 2011-11-08 at 15:43 +, Simon Marlow wrote: Hmm, but there is something you could do. Suppose a thread could be in a mode in which instead of blocking on a BLACKHOLE it would

heads up: GHC gets a new constraint solver (again)

2011-11-16 Thread Dimitrios Vytiniotis
Friends, After a very busy period of hard work with Simon, we've re-engineered GHCs constraint solver and I just pushed a big patch on master along with modifications in the testsuite. The new constraint solver is based on the existing in its core ideas but is shorter, much cuter, and for

Re: heads up: GHC gets a new constraint solver (again)

2011-11-16 Thread Daniel Fischer
On Wednesday 16 November 2011, 19:22:53, Dimitrios Vytiniotis wrote: Friends, After a very busy period of hard work with Simon, we've re-engineered GHCs constraint solver and I just pushed a big patch on master along with modifications in the testsuite. The new constraint solver is based

Re: Why not allow empty record updates?

2011-11-16 Thread wren ng thornton
On 11/15/11 8:07 PM, wagne...@seas.upenn.edu wrote: Quoting wren ng thornton w...@freegeek.org: So far I've just defined helper functions to adjust the phantom type[1], each of which is implemented by (\x - x { foo = foo x }). It's a horrible hack, but at least it's hidden away in library