Re: [racket-dev] Short-circuiting comprehensions

2012-09-18 Thread Eli Barzilay
On Friday, Matthew Flatt wrote: > > Meanwhile, to support breaking after the current element, I'm trying > out `#:final'. A `#:final' clause is like `#:break', except that it > ends the loop after the next run of the body. [...] (When I first saw this, I thought that it was a kind of a "the value

Re: [racket-dev] Segmentation fault 11?

2012-09-18 Thread Danny Yoo
On Tuesday, September 18, 2012, Matthew Flatt wrote: > I wasn't able to replicate the crash. Does it happen consistently for > you in v5.3? In v5.3.0.24? > It's consistent for me in 5.3. I can come in the morning with the laptop to show you. _ Racket Developers list:

Re: [racket-dev] Segmentation fault 11?

2012-09-18 Thread Matthew Flatt
I wasn't able to replicate the crash. Does it happen consistently for you in v5.3? In v5.3.0.24? At Mon, 17 Sep 2012 21:07:43 -0600, Danny Yoo wrote: > I'm seeing weirdness when trying to import Dave Herman's memoize > package on Racket 5.3: > > ;;; > > (require (planet dherman/memoize:3:

Re: [racket-dev] Top level is hopeless or bug?

2012-09-18 Thread Matthew Flatt
At Mon, 17 Sep 2012 23:48:06 -0400, Asumu Takikawa wrote: > Is the following interaction the expected behavior here or is it a bug? > > Welcome to Racket v5.3.0.24. > -> (module foo racket (define x 0) (provide x)) > -> (require 'foo) > -> x > 0 > -> (module foo racket (module* bar #f (define x 1)