From: Peter Zotov <whitequark@whitequark.org>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Raoul Duke <raould@gmail.com>, OCaml <caml-list@inria.fr>,
caml-list-request@inria.fr
Subject: Re: [Caml-list] [ANN] OCaml-Java is going alpha, to github
Date: Tue, 15 Jul 2014 16:11:58 +0400 [thread overview]
Message-ID: <40448e4581a57924e4eca25df7b5b61b@whitequark.org> (raw)
In-Reply-To: <1405417081.4384.182.camel@e130>
On 2014-07-15 13:38, Gerd Stolpmann wrote:
> Go is in particular interesting because it provides a model of
> lightweight threading that can be backed by multiple cores.
You may want to know that Go is not memory-safe in presence of
race conditions. It uses multi-word fat pointers that cannot be
atomically updated, yet does not globally protect them with a mutex
"for speed", or prevent such updates using the type system.
--
Peter Zotov
sip:whitequark@sipnet.ru
next prev parent reply other threads:[~2014-07-15 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 22:15 xclerc
2014-07-14 22:21 ` Raoul Duke
2014-07-15 9:38 ` Gerd Stolpmann
2014-07-15 12:11 ` Peter Zotov [this message]
2014-07-15 22:52 ` Gerd Stolpmann
2014-07-16 7:44 ` Jacques du Preez
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=40448e4581a57924e4eca25df7b5b61b@whitequark.org \
--to=whitequark@whitequark.org \
--cc=caml-list-request@inria.fr \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=raould@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