The gen:stream documentation has this example:
(define-struct list-stream (v)
#:methods gen:stream
[(define (stream-empty? stream)
(empty? (list-stream-v stream)))
(define (stream-first stream)
(first (list-stream-v stream)))
(define (stream-rest stream)
Hi all,
about the future of Racket... A professional fortune teller here.
2040 -- I clearly see #lang racket widely used, although there are many more
#langs out there (which translate to #lang racket under the hood).
The peak popularity of infix notational Racket has passed, now it's in the
Hi Sam,
that is a very load and clear answer, which is encouriging for everyone
having an interest in current Racket.
Very glad to have this black on white from an authorative person in the
community.
Best wishes.
Op maandag 26 augustus 2019 17:08:08 UTC+2 schreef Sam Tobin-Hochstadt:
>
>
Good to know. If I come off as anything inconvenient please tell me and I will
stop immediately.
-slg
Original Message
On Aug 26, 2019, 12:41 PM, Sam Tobin-Hochstadt wrote:
> Posting exciting content about Racket on this list is 100% welcome.
>
> Sam
>
> On Sun, Aug 25, 2019
Thanks! I'm glad you guys enjoyed it. Your patchwork design was very nice
as well Daniel.
Definitely let me know if you encounter any problems when using it. I plan
to uploading the package soon as well.
- Zac
25 Ağustos 2019 Pazar 18:52:18 UTC tarihinde Zachary Romero yazdı:
>
> Hello,
>
>
I haven't been able to find a persistent job queue for Racket, so I thought
I'd ask if one exists before writing a simple one. I did see Jay's job
queue package, but it doesn't appear to persist to disk, and that is a
requirement.
I typically use Postgres for my apps, and I would prefer to
Racket as a project has both a strong commitment to keeping everything
running long into the future and to extensive documentation. `#lang racket`
will continue to be available, working, and will continue to have
documentation.
Sam
On Mon, Aug 26, 2019 at 4:45 AM Arie van Wingerden
wrote:
>
On Monday, August 26, 2019 at 4:45:44 AM UTC-4, Arie van Wingerden wrote:
>
> When Racket2 was announced, I got really upset, being afraid that all what
> I like about (the old) Racket would be at stake. Also it was mentioned that
> the docs would be based on Racket2 syntax, which probably would
Hello,
Please, find below the first call for participation for IFL 2019.
Please forward these to anyone you think may be interested.
Apologies for any duplicates you may receive.
best regards,
Jurriaan Hage
Publicity Chair of IFL
On Mon, Aug 26, 2019 at 01:45:44AM -0700, Arie van Wingerden wrote:
> When Racket2 was announced, I got really upset, being afraid that all what I
> like about (the old) Racket would be at stake. Also it was mentioned that the
> docs would be based on Racket2 syntax, which probably would hamper
When Racket2 was announced, I got really upset, being afraid that all what I
like about (the old) Racket would be at stake. Also it was mentioned that the
docs would be based on Racket2 syntax, which probably would hamper using them
for old school Racket.
I really think that old school Racket
11 matches
Mail list logo
