From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] benefits of rust
Date: Sat, 14 Mar 2020 22:42:55 -0700
Message-ID: <CAC2bXD6YqKtHmLLhN6NPfCQtd=+JZEtE9VfHj9aispT3kQt18Q@mail.gmail.com> (raw)
In-Reply-To: <20200315051821.ha7d2ngus6x73rzb@topoi.pooq.com>
On Sat, Mar 14, 2020, 22:18 Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> The one drawback I see to Rust is that it doesn't have a
> garbage-collected scope or storage class. There are programming
> techniques that involve complexly tangled data structure. Rust is
> not good for such problems.
>
Rust has support for reference counted smart pointers in the standard
library (Arc (atomic) and Rc (non-atomic)), where those aren't sufficient,
there are libraries for arenas (what I'm using in Kazan for compiler
data-structures (see shader-compiler-ir in the git repo) -- also used in
the rust compiler itself) as well as experimental libraries for full
garbage collection:
see shifgrethor for one of the more interesting GC libraries written by a
core rust contributor:
https://internals.rust-lang.org/t/shifgrethor-garbage-collection-as-a-rust-library/8597
Incidentally, I am also writing a custom garbage collector in Rust for the
next version of my Minecraft-style game engine (Voxels) -- I'm using a 3D
variant of the hashlife algorithm (see wikipedia) which uses a garbage
collector except that the more garbage is kept around the faster it runs
(opposite of most GCs) since it is used to cache computations.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPweEDyGztErPRa=9KLM9J02R1fLQ9Y23VY7UNAkfJ5yt-03PQ@mail.gmail.com>
[not found] ` <20200220093921.635c47f72ea2faf85dd352b7@gmx.com>
2020-03-12 14:32 ` [libre-riscv-dev] next tasks Hendrik Boom
2020-03-12 14:43 ` Luke Kenneth Casson Leighton
2020-03-12 17:40 ` Jacob Lifshay
2020-03-13 6:44 ` Lauri Kasanen
2020-03-13 7:38 ` Jacob Lifshay
2020-03-13 8:04 ` Lauri Kasanen
2020-03-13 8:25 ` Jacob Lifshay
2020-03-13 10:13 ` Luke Kenneth Casson Leighton
2020-03-13 18:10 ` [libre-riscv-dev] Rustup security Jacob Lifshay
2020-03-14 18:13 ` [libre-riscv-dev] next tasks Hendrik Boom
2020-03-14 18:23 ` whygee
2020-03-14 18:28 ` Luke Kenneth Casson Leighton
2020-03-14 18:49 ` whygee
2020-03-15 2:47 ` [libre-riscv-dev] benefits of rust Jacob Lifshay
2020-03-15 5:18 ` Hendrik Boom
2020-03-15 5:42 ` Jacob Lifshay [this message]
2020-03-15 5:47 ` [libre-riscv-dev] [OT] Minecraft garbage collection Hendrik Boom
2020-03-15 6:41 ` Jacob Lifshay
2020-03-15 12:11 ` Luke Kenneth Casson Leighton
2020-03-16 13:22 ` Luke Kenneth Casson Leighton
2020-03-16 16:22 ` Jacob Lifshay
2020-03-16 16:24 ` Luke Kenneth Casson Leighton
2020-03-17 18:23 ` [libre-riscv-dev] next tasks Jacob Lifshay
2020-03-17 18:56 ` Luke Kenneth Casson Leighton
2020-03-16 18:30 ` Immanuel, Yehowshua U
2020-03-16 18:51 ` Jacob Lifshay
2020-03-16 22:53 ` Luke Kenneth Casson Leighton
2020-03-16 22:53 ` Luke Kenneth Casson Leighton
2020-03-16 23:12 ` Immanuel, Yehowshua U
2020-03-16 23:16 ` Immanuel, Yehowshua U
2020-03-16 23:42 ` Luke Kenneth Casson Leighton
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='CAC2bXD6YqKtHmLLhN6NPfCQtd=+JZEtE9VfHj9aispT3kQt18Q@mail.gmail.com' \
--to=programmerjake@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git