[racket-users] gen:stream doc fix?
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) (rest (list-stream-v stream)))]) I believe this example is broken in a sneaky way; the “stream-rest” operation returns a simple list rather than a list-stream. This happens to “work” wrt things like stream-rest and stream-first because lists are also streams. I claim that this should instead read: (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) (list-stream (rest (list-stream-v stream]) Can someone confirm that this is just a typo? John -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/707f6164-d28e-4191-bf13-313edac3d5f0%40mtasv.net.
[racket-users] Re: The future of current language Racket
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 decline, but still widely used. Arithmetic expressions can be included in s-expression code by simply wrapping them with $ signs, like in Latex. PLT team gets a Turing award for their contributions to programming language research and CS education. CS majors are required to take a macros exam and demonstrate solid knowledge of both reader macros and compile macros to get a degree. I. Am Montag, 26. August 2019 11:45:44 UTC+3 schrieb Arie van Wingerden: > > 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 should be saved for the future, > because it is the Scheme to go for many reasons e.g. superb IDE + debugging > and many good packages and of course the whole creative eco system. > > Question 1: > Please can you explicitly guarantee that Racket (#lang racket) will be > available for the future? > > Question 2: > Can you explicitely guarantee that the documentation for #lang racket will > be available in the future? > > Please know that I love DrRacket as a whole and that I am not against > Racket2 at all. I just like my favorite old Racket language to be available > forever😊 > > Many thx for DrRacket and keep up the good work! > > Best wishes. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/cd9365d5-0ac4-4e44-ad78-e45f084fb847%40googlegroups.com.
Re: [racket-users] The future of current language Racket
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: > > 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: > >> 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 should be saved for the future, >> because it is the Scheme to go for many reasons e.g. superb IDE + debugging >> and many good packages and of course the whole creative eco system. >> >> Question 1: >> Please can you explicitly guarantee that Racket (#lang racket) will be >> available for the future? >> >> Question 2: >> Can you explicitely guarantee that the documentation for #lang racket >> will be available in the future? >> >> Please know that I love DrRacket as a whole and that I am not against >> Racket2 at all. I just like my favorite old Racket language to be available >> forever😊 >> >> Many thx for DrRacket and keep up the good work! >> >> Best wishes. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to racket...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/racket-users/db031d63-adc3-4217-aa54-e1a727d61a94%40googlegroups.com >> . >> > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/485ea5f3-4af6-4d62-80e6-1fb133398771%40googlegroups.com.
Re: [racket-users] Where is the best place to post regular content about Racket projects?
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 at 4:23 PM Sage Gerard wrote: >> >> I am producing videos and blog posts around my Racket projects. I don't want >> to announce each one here if it's poor etiquette/unwanted solicitation. >> >> Still, I would like to have a platform to share regular content with Racket >> users with the intent to promote my work. Is there a canonical place to do >> that? (Currently assuming the r/Racket subreddit). >> >> ~slg >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to racket-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/racket-users/AaFsetTXstoO14PBPPULsvIglvkySueLG-9yxIdIoDfCMOZTTd1tNyfmwOBnQhlDcIPrN__5WlfMKyB18pNZhQvETUawCbjN28s1EpKZfBU%3D%40sagegerard.com. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/pYMTXXamfiMK64h8YJou8mu9vDSq3bZXeJAS5tuQnEAtbsQ6mEecvTs6Un7s3Xt4cSE8Q0UFH2IRpge9LmCrRqDSrzrVvH4HfQKzKJSWYi4%3D%40sagegerard.com.
[racket-users] Re: [standard-fish] A geometric design
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, > > Here is a little tessellation design I made along with some helper > functions to generate them: https://github.com/zkry/tessellation . I'm > new to Racket and this was a great chance to practice. Thanks for this > idea! > > -- Zac > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/bdae1e91-4169-4a98-b42f-2e5b7f8a5870%40googlegroups.com.
[racket-users] Persistent job queue
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 also use Postgres for the persistence of the job queue to avoid introducing something new (e.g. Redis) to my server setup. Amazon RDS provides great multi-site availability, so I want to continue to leverage that. Thanks, Brian Adkins -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/8a87e815-0519-47bf-b04b-93c9be3487f5%40googlegroups.com.
Re: [racket-users] The future of current language Racket
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: > 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 should be saved for the future, > because it is the Scheme to go for many reasons e.g. superb IDE + debugging > and many good packages and of course the whole creative eco system. > > Question 1: > Please can you explicitly guarantee that Racket (#lang racket) will be > available for the future? > > Question 2: > Can you explicitely guarantee that the documentation for #lang racket will > be available in the future? > > Please know that I love DrRacket as a whole and that I am not against > Racket2 at all. I just like my favorite old Racket language to be available > forever😊 > > Many thx for DrRacket and keep up the good work! > > Best wishes. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/db031d63-adc3-4217-aa54-e1a727d61a94%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAK%3DHD%2BZDLkAnjJo2wNLBYbw3ap1y64zyxCb6epjXyHvsWi8NXQ%40mail.gmail.com.
[racket-users] Re: The future of current language Racket
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 hamper > using them for old school Racket. > > I really think that old school Racket should be saved for the future, > because it is the Scheme to go for many reasons e.g. superb IDE + debugging > and many good packages and of course the whole creative eco system. > > Question 1: > Please can you explicitly guarantee that Racket (#lang racket) will be > available for the future? > > Question 2: > Can you explicitely guarantee that the documentation for #lang racket will > be available in the future? > > Please know that I love DrRacket as a whole and that I am not against > Racket2 at all. I just like my favorite old Racket language to be available > forever😊 > > Many thx for DrRacket and keep up the good work! > > Best wishes. The Racket project leadership will be offering clarification once they're able to meet together, see the following: https://groups.google.com/d/msg/racket-users/9Eh9H1Jt28Q/2Wx7xopIDAAJ I can empathize with your concern, but I am no longer concerned about the future of #lang racket. There are simply too many great things about it for it not to continue, and in a very unlikely worst case scenario, in my opinion, it would be easier to fork the software and continue to maintain/enhance it then it would be to bring another Scheme, such as Chez, up to the same productivity level. And to be clear, I do *not* at all expect the worst case scenario :) Since my post (referenced above), I have decided to not wait for the Racket project leadership, and have gone "all in" with #lang racket, and I plan on continuing with that attitude for the foreseeable future. I expect to be able to add some new packages to the great set we already have before the new syntax is completed :) Brian Adkins -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/ac9c845d-ea8d-47a2-94d5-1a3a21687f80%40googlegroups.com.
[racket-users] First call for participation for IFL 2019 (Implementation and Application of Functional Languages)
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
IFL 2019
31st Symposium on Implementation and Application of Functional Languages
National University of Singapore
September 25th-27th, 2019
http://2019.iflconference.org
### Scope
The goal of the IFL symposia is to bring together researchers actively
engaged
in the implementation and application of functional and function-based
programming languages. IFL 2019 will be a venue for researchers to present
and
discuss new ideas and concepts, work in progress, and publication-ripe
results
related to the implementation and application of functional languages and
function-based programming.
Topics of interest to IFL include, but are not limited to:
- language concepts
- type systems, type checking, type inferencing
- compilation techniques
- staged compilation
- run-time function specialization
- run-time code generation
- partial evaluation
- (abstract) interpretation
- metaprogramming
- generic programming
- automatic program generation
- array processing
- concurrent/parallel programming
- concurrent/parallel program execution
- embedded systems
- web applications
- (embedded) domain specific languages
- security
- novel memory management techniques
- run-time profiling performance measurements
- debugging and tracing
- virtual/abstract machine architectures
- validation, verification of functional programs
- tools and programming techniques
- (industrial) applications
### Keynote Speaker
* Olivier Danvy, Yale-NUS College
### Submissions and peer-review
Differently from previous editions of IFL, IFL 2019 solicits two kinds of
submissions:
* Regular papers (12 pages including references)
* Draft papers for presentations ('weak' limit between 8 and 15 pages)
Regular papers will undergo a rigorous review by the program committee, and
will
be evaluated according to their correctness, novelty, originality,
relevance,
significance, and clarity. A set of regular papers will be conditionally
accepted for publication. Authors of conditionally accepted papers will be
provided with committee reviews along with a set of mandatory revisions.
Regular papers not accepted for publication will be considered as draft
papers, at the request of the author.
Draft papers will be screened to make sure that they are within the scope of
IFL, and will be accepted for presentation or rejected accordingly.
Prior to the symposium:
Authors of conditionally accepted papers and accepted presentations will
submit a pre-proceedings version of their work that will appear in the
draft
proceedings distributed at the symposium. The draft proceedings does not
constitute a formal publication.
We require that at least one of the authors present the work at IFL 2019.
After the symposium:
Authors of conditionally accepted papers will submit a revised versions of
their paper for the formal post-proceedings.
The program committee will assess whether the mandatory revisions have
been
adequately addressed by the authors and thereby determines the final
accept/reject status of the paper.
Our interest is to ultimately accept all conditionally accepted papers.
If you
are an author of a conditionally accepted paper, please make sure that you
address all the concerns of the reviewers.
Authors of accepted presentations will be given the opportunity to
incorporate
the feedback from discussions at the symposium and will be invited to
submit a
revised full article for the formal post-proceedings.
The program committee will evaluate these submissions according to their
correctness, novelty, originality, relevance, significance, and clarity,
and
will thereby determine whether the paper is accepted or rejected.
### Publication
The formal proceedings will appear in the International Conference
Proceedings Series of the ACM Digital Library.
At no time may work submitted to IFL be simultaneously submitted to other
venues; submissions must adhere to ACM SIGPLAN's republication policy:
http://www.sigplan.org/Resources/Policies/Republication
### Important dates
Submission of regular papers: June 15, 2019
Submission of draft papers: August1, 2019
Regular papers notification:August1, 2019
Regular draft papers notification: August7, 2019
Deadline for early registration:August 31, 2019
Submission of pre-proceedings version: September15,
Re: [racket-users] The future of current language Racket
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 using them > for old school Racket. > > I really think that old school Racket should be saved for the future, because > it is the Scheme to go for many reasons e.g. superb IDE + debugging and many > good packages and of course the whole creative eco system. > > Question 1: > Please can you explicitly guarantee that Racket (#lang racket) will be > available for the future? > > Question 2: > Can you explicitely guarantee that the documentation for #lang racket will be > available in the future? > > Please know that I love DrRacket as a whole and that I am not against Racket2 > at all. I just like my favorite old Racket language to be available forever😊 Arguing from history: Every attempt to replace Lisp syntax over the last 50 years has failed. Some of the have produced new syntaxes that have prospered (such as javascript and our own Scribble), but none have ever displaced S-expressions. I have no fears about this. -- hendrik -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/20190826132846.qvuxx3hyedx2dto5%40topoi.pooq.com.
[racket-users] The future of current language Racket
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 should be saved for the future, because it is the Scheme to go for many reasons e.g. superb IDE + debugging and many good packages and of course the whole creative eco system. Question 1: Please can you explicitly guarantee that Racket (#lang racket) will be available for the future? Question 2: Can you explicitely guarantee that the documentation for #lang racket will be available in the future? Please know that I love DrRacket as a whole and that I am not against Racket2 at all. I just like my favorite old Racket language to be available forever😊 Many thx for DrRacket and keep up the good work! Best wishes. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/db031d63-adc3-4217-aa54-e1a727d61a94%40googlegroups.com.
