From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
Cc: Duncan Mak <duncanmak@gmail.com>,
kawa mailing list <kawa@sourceware.org>
Subject: Re: First-class continuations in Kawa
Date: Sat, 01 May 2021 15:06:47 -0400 [thread overview]
Message-ID: <23585.1619896007@localhost> (raw)
In-Reply-To: Your message of "Sat, 01 May 2021 21:45:59 +0300." <CAPh7weAfU3DGr09HzPBG34R0xi6xtKW2jWndNYa9b2cj++NVBg@mail.gmail.com>
Hopefully this isn't considered noise but I thought I'd add a brief note
as a Kawa user: It would be really great to have support for first-class
continuations. I recall several instances when I wanted to use some
portable library (typically from snow-fort.org) and hit a roadblock due
to continuations. And similarly with some SRFI sample implementations.
A question to the implementation-savvy: Would the only downside of
enabling first-class continuations (assuming they have been implemented
of course) be potentially lower performance? Or would there be some
compatibility issues with other JVM languages and libraries?
For instance, would using some Java library such as okhttp pose any
issues other than a potential modest performance hit?
In any case, thanks to all involved in this effort.
Regards,
-chaw
next prev parent reply other threads:[~2021-05-01 19:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 0:49 Duncan Mak
2018-01-20 6:47 ` Per Bothner
2018-01-20 16:07 ` Duncan Mak
2018-01-20 23:20 ` Andrea Bernardini
2018-02-21 0:21 ` Andrea Bernardini
2018-02-22 0:38 ` Duncan Mak
2021-05-01 16:15 ` Duncan Mak
2021-05-01 18:45 ` Arvydas Silanskas
2021-05-01 19:06 ` Sudarshan S Chawathe [this message]
2021-05-01 20:38 ` Per Bothner
2021-06-09 9:04 ` Arvydas Silanskas
2021-06-09 23:27 ` Per Bothner
2021-08-08 14:29 ` Arvydas Silanskas
2021-08-08 15:53 ` Andrea Bernardini
2021-08-08 23:52 ` Per Bothner
2021-08-09 19:41 ` Per Bothner
2022-12-07 23:42 ` Duncan Mak
2022-12-09 10:53 ` Arvydas Silanskas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23585.1619896007@localhost \
--to=chaw@eip10.org \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=nma.arvydas.silanskas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).