From: Stuff Received <stuff@riddermarkfarm.ca>
To: tuhs@tuhs.org
Subject: [TUHS] Re: yet another C discussion (YACD) and: Rust is not C++
Date: Mon, 30 Jan 2023 16:37:45 -0500 [thread overview]
Message-ID: <9f37402c-6773-deb6-651e-0287bf100bfd@riddermarkfarm.ca> (raw)
In-Reply-To: <CAP6exYJ8S--bhw6wm88JMeJKYiTW0tx_JD-au8NACaoAkQjiOA@mail.gmail.com>
On 2023-01-30 14:35, ron minnich wrote (in part):
> As for replacing C, the velocity of Rust is just astonishing. I think
> folks have been waiting for something to replace C for a long time, and
> Rust, with all its headaches and issues, is likely to be that thing.
Of possible interest:
https://devclass.com/2023/01/23/rust-has-no-formal-specification-and-it-is-time-that-was-fixed-says-team-which-longs-for-formalized-type-system/
N.
next prev parent reply other threads:[~2023-01-30 21:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 17:24 [TUHS] " ron minnich
2023-01-30 18:47 ` [TUHS] " Andy Kosela
2023-01-30 18:59 ` segaloco via TUHS
2023-01-30 19:35 ` ron minnich
2023-01-30 21:37 ` Stuff Received [this message]
2023-01-31 1:47 ` Alejandro Colomar
2023-01-31 2:55 ` Dan Cross
2023-01-31 3:59 ` ron minnich
2023-01-31 12:26 ` Dan Cross
2023-02-01 0:40 ` Steffen Nurpmeso
2023-02-01 0:49 ` Larry McVoy
2023-02-01 1:03 ` Luther Johnson
[not found] ` <EjVurdhKm6O8BZ9n0FesPIsZH6sArmVbEN_ikfso8aNlawWIe8ElCGwgaT4ydoWHMNvRty9jDPxFxhLXVXGMjwsTfmfgLgKXcfjpLmqENT8=@protonmail.com>
2023-02-01 2:22 ` [TUHS] Re: yet another C discussion (YACD) Warren Toomey via TUHS
2023-02-01 0:50 ` [TUHS] Algol rules: was something about Rust is not C++ Will Senn
2023-02-01 1:18 ` [TUHS] " Chet Ramey
2023-02-01 1:24 ` Luther Johnson
2023-02-01 0:53 ` [TUHS] Re: yet another C discussion (YACD) and: " Steffen Nurpmeso
2023-02-01 16:34 ` Luther Johnson
2023-01-31 14:15 ` Blake McBride
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=9f37402c-6773-deb6-651e-0287bf100bfd@riddermarkfarm.ca \
--to=stuff@riddermarkfarm.ca \
--cc=tuhs@tuhs.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).