From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Compilation semantics for static garbage collection
Date: Thu, 18 Jun 2015 15:44:32 -0400 [thread overview]
Message-ID: <CAK7rcp8-tBP1=kGK2fGHWnppUrkRe+U7vSEScRg4nL-qCgtfNg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
I was thinking that while rust is new, some of what it is pioneering is
really interesting, especially with the way it deals with ownership being a
type. Rust doesn't have a GC, yet it rules out leakage and remains fast. It
also manages concurrency safety very well.
The stipulations put on types in the ocaml language are pretty strict, and
the GC is transparent to the user. What is the possibility that there could
ever be a version of ocaml that makes use of something like ownership or
some typing mechanism to determine more at compile time, to facilitate the
removal or reduction of the GC?
[-- Attachment #2: Type: text/html, Size: 638 bytes --]
next reply other threads:[~2015-06-18 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 19:44 Kenneth Adam Miller [this message]
2015-06-18 21:59 ` Malcolm Matalka
2015-06-18 22:25 ` Gabriel Scherer
2015-06-19 2:00 ` Kenneth Adam Miller
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='CAK7rcp8-tBP1=kGK2fGHWnppUrkRe+U7vSEScRg4nL-qCgtfNg@mail.gmail.com' \
--to=kennethadammiller@gmail.com \
--cc=caml-list@inria.fr \
/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).