No subject
Tue Feb 1 14:29:29 CET 2011
in the code for 'doesntWork' so I doubt that a new implementation of timeout
would fix it, but I thought I'd ask :)
It's super annoying, especially when it happens when you're not expecting
it.
(btw, I've only tested the above code in ghc 6.x, so I have no idea if the
behavior is the same in 7)
- Job
On Mon, Feb 21, 2011 at 3:39 PM, Bas van Dijk <v.dijk.bas at gmail.com> wrote:
> On 19 February 2011 00:04, Bas van Dijk <v.dijk.bas at gmail.com> wrote:
> > So, since the new implementation is not really faster in a
> > representative benchmark and above all is buggy, I'm planning to ditch
> > it in favour of the event-manager based timeout.
>
> The patch is ready for review:
>
>
> http://hackage.haskell.org/trac/ghc/attachment/ticket/4963/faster_timeout.dpatch
>
> Bas
>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
--bcaec51d21a0234be0049cd150fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div>I'm curious, is it possible that your new timeout implementation w=
ould fix this problem?:</div><div><br></div><div>doesntWork :: Int -> In=
t</div><div>doesntWork x =3D last $ cycle [x]</div><div><br></div><div>test=
:: IO (Maybe Bool)</div>
<div>test =3D timeout 1 $ evaluate $ doesntWork 5 =3D=3D 5 -- never termina=
tes, even with the timeout</div><div><br></div><div>From what I can gather,=
this problem is caused by a lack of context switches in the code for '=
doesntWork' so I doubt that a new implementation of timeout would fix i=
t, but I thought I'd ask :)</div>
<div><br></div><div>It's super annoying, especially when it happens whe=
n you're not expecting it.</div><div><br></div><div>(btw, I've only=
tested the above code in ghc 6.x, so I have no idea if the behavior is the=
same in 7)</div>
<div><br></div><div>- Job</div><br><div class=3D"gmail_quote">On Mon, Feb 2=
1, 2011 at 3:39 PM, Bas van Dijk <span dir=3D"ltr"><<a href=3D"mailto:v.=
dijk.bas at gmail.com">v.dijk.bas at gmail.com</a>></span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">
<div class=3D"im">On 19 February 2011 00:04, Bas van Dijk <<a href=3D"ma=
ilto:v.dijk.bas at gmail.com">v.dijk.bas at gmail.com</a>> wrote:<br>
> So, since the new implementation is not really faster in a<br>
> representative benchmark and above all is buggy, I'm planning to d=
itch<br>
> it in favour of the event-manager based timeout.<br>
<br>
</div>The patch is ready for review:<br>
<br>
<a href=3D"http://hackage.haskell.org/trac/ghc/attachment/ticket/4963/faste=
r_timeout.dpatch" target=3D"_blank">http://hackage.haskell.org/trac/ghc/att=
achment/ticket/4963/faster_timeout.dpatch</a><br>
<div><div></div><div class=3D"h5"><br>
Bas<br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href=3D"mailto:Haskell-Cafe at haskell.org">Haskell-Cafe at haskell.org</a><br=
>
<a href=3D"http://www.haskell.org/mailman/listinfo/haskell-cafe" target=3D"=
_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br>
--bcaec51d21a0234be0049cd150fa--
More information about the Haskell-Cafe
mailing list