From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] Spew's Concurrency Extension
Date: Sat, 2 Jul 2016 09:57:04 +0900 [thread overview]
Message-ID: <365967b16684f2c26442fccbebd83889@mars.jitaku.localdomain> (raw)
In-Reply-To: <CAAsuYKdk==tKjQR5vvneQzz5NKj2KiSHHmdgA9kwjH6_WwGq+Q@mail.gmail.com>
> Hello everybody!
>
> Attached is a paper describing the concurrency extension I wrote.
I liked Alef, because it's very clear, and then easy to understand
what is concurrency programming.
Your paper looks like such to me.
Please go ahead, and make it _solid_ to be able to use everywhere
in Plan 9, and included in the standard distribution.
Anyone's comment?
Kenji
next prev parent reply other threads:[~2016-07-02 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 19:45 Benjamin Purcell
2016-07-02 0:57 ` kokamoto [this message]
2016-07-02 12:07 ` [9front] " cinap_lenrek
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=365967b16684f2c26442fccbebd83889@mars.jitaku.localdomain \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).