[racket] future

At Mon, 29 Aug 2011 15:22:14 -0500, Robby Findler wrote:
> as-current-continuation? as-output-file*? as-output-bytes? There are a
> lot of these. Is someone up for going through the list sorting this
> out properly?

To me, `as-thread' and `as-future' indicate forms that produce a thread
and a future, respectively. I don't think the ones you're listing here
fit into that pattern.

More generally, I agree that the `with-...' function names are
unfortunate, while I'm not convinced that all the `call-with-...'
functions need syntactic-form variants (but, for ones that do, a
`with-' binding form seems likely the way to go).


> On Mon, Aug 29, 2011 at 3:16 PM, Matthias Felleisen
> <matthias at ccs.neu.edu> wrote:
> >
> > as-output-file
> >
> >
> > On Aug 29, 2011, at 4:00 PM, Matthew Flatt wrote:
> >
> >> At Mon, 29 Aug 2011 15:51:20 -0400, Eli Barzilay wrote:
> >>> 20 minutes ago, Shriram Krishnamurthi wrote:
> >>>> I like it.
> >>>>
> >>>> I'm afraid I just don't understand Eli's response to this...
> >>>
> >>> It's unrelated to the name: you see `as-thread' and `thread',
> >>> `as-future' and `future', and you learn the difference.  Then you see
> >>> `as-delay' and you get surprised that `delay' is not expecting a
> >>> thunk.
> >>
> >> I included `as-delay' only for consistency (I thought) with the earlier
> >> lists, so let's skip it.
> >>
> >> _________________________________________________
> >>  For list-related administrative tasks:
> >>  http://lists.racket-lang.org/listinfo/users
> >
> > _________________________________________________
> >  For list-related administrative tasks:
> >  http://lists.racket-lang.org/listinfo/users
> >