From: Po Lu <luangruo@yahoo.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Troy Hinckley <comms@dabrev.com>,
Sean Allred <allred.sean@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Consideration for Rust contributions in Emacs
Date: Tue, 24 Jan 2023 08:45:43 +0800 [thread overview]
Message-ID: <875ycw69qg.fsf@yahoo.com> (raw)
In-Reply-To: <87zga9tln8.fsf@web.de> (Arne Babenhauserheide's message of "Mon, 23 Jan 2023 14:21:58 +0100")
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> GCCrs might help with that: https://rust-gcc.github.io/
>
> Once that’s released and stable in GCC, Rust is finally safe to use for
> those who want at least two independent implementations (like me).
The language standard library must also be ported to both the Unix and
DJGPP platforms. On MS-DOS, it must also be made unexec ready, because
only the unexec build is supported there.
> Also the gains from memory safety are much lower than for much other
> software, because in Emacs memory-safety is already provided by elisp.
Has anyone even demonstrated that memory safety is a problem for Emacs?
The only program where it matters, that runs on most computers, is a web
browser. And even there it only papers over the more fundamental
problem, which is that web browsers provide an easy means to run
proprietary JavaScript code without the user even knowing it exists.
next prev parent reply other threads:[~2023-01-24 0:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f2ee2f1d-332f-4707-bd9e-23444c34749f@Spark>
2023-01-21 22:48 ` Consideration for Rust contributions in Emacs Troy Hinckley
2023-01-22 7:44 ` Po Lu via Emacs development discussions.
2023-01-22 11:05 ` Daniel Martín
2023-01-22 14:04 ` Po Lu
2023-01-22 23:16 ` Troy Hinckley
2023-01-23 5:55 ` Po Lu
2023-01-24 3:49 ` Richard Stallman
2023-01-24 3:52 ` Richard Stallman
2023-01-24 6:52 ` Dr. Arne Babenhauserheide
2023-01-23 2:00 ` Sean Allred
2023-01-23 3:37 ` Troy Hinckley
2023-01-23 12:25 ` Po Lu
2023-01-24 2:24 ` Lynn Winebarger
2023-01-24 2:47 ` Etienne Prud'homme
2023-01-24 2:49 ` Po Lu
2023-04-11 12:39 ` Po Lu via Emacs development discussions.
2023-04-11 18:23 ` Dr. Arne Babenhauserheide
2023-04-15 3:36 ` Richard Stallman
2023-04-15 3:40 ` Po Lu
2023-04-15 7:03 ` Eli Zaretskii
2023-04-12 0:36 ` Dmitry Gutov
2023-04-12 4:59 ` tomas
2023-04-12 11:26 ` Richard Stallman
2023-04-13 1:02 ` Richard Stallman
2023-04-13 5:09 ` Eli Zaretskii
2023-04-13 8:23 ` Po Lu
2023-04-15 23:27 ` Dmitry Gutov
2023-04-16 0:11 ` Po Lu
2023-04-17 2:55 ` Richard Stallman
2023-01-23 13:21 ` Dr. Arne Babenhauserheide
2023-01-23 16:51 ` John Yates
2023-01-23 17:06 ` Eli Zaretskii
2023-01-23 18:22 ` John Yates
2023-01-23 19:04 ` Eli Zaretskii
2023-01-23 19:44 ` Bob Rogers
2023-01-23 19:56 ` Eli Zaretskii
2023-01-23 20:08 ` Bob Rogers
2023-01-23 19:22 ` Dr. Arne Babenhauserheide
2023-01-23 23:52 ` Po Lu
2023-01-24 0:45 ` Po Lu [this message]
2023-01-23 7:32 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ycw69qg.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=allred.sean@gmail.com \
--cc=arne_bab@web.de \
--cc=comms@dabrev.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).