From: Blake McBride <blake1024@gmail.com>
To: ron minnich <rminnich@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: yet another C discussion (YACD) and: Rust is not C++
Date: Tue, 31 Jan 2023 08:15:29 -0600 [thread overview]
Message-ID: <CABwHSOtMdM6SvMhtHuXouH1SktU_NR0k_Y=+RCyHJ_9KepTvbA@mail.gmail.com> (raw)
In-Reply-To: <CAP6exY+_YKkJ2vHpz2sk-yjoDCnyx8g4jW_Lk3qynGV1cCuEOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Although few will admit when their uneducated opinion is wrong, it is true
that Rust and C++ are very different. They are as different as any two
clearly different languages are. Their respective feature sets are quite
different and do not overlap any more than any two totally different
languages do.
Blake McBride
On Mon, Jan 30, 2023 at 11:26 AM ron minnich <rminnich@gmail.com> wrote:
> I did not want to disrupt the FD 2 discussion, but I could not really let
> this comment go unanswered:
>
> "Smells like C++ to me. Rust in essence is a re-implementation of C++ not
> C. It tries to pack as much features as it possibly can. "
>
> It's hard for me to see how you can say this if you have done any work in
> Rust and C++.
>
> But, short form: Rust is not C++. Full stop.
>
> I did not feel that comment should go unanswered, lest people believe it.
>
[-- Attachment #2: Type: text/html, Size: 1306 bytes --]
prev parent reply other threads:[~2023-01-31 14:16 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
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 [this message]
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='CABwHSOtMdM6SvMhtHuXouH1SktU_NR0k_Y=+RCyHJ_9KepTvbA@mail.gmail.com' \
--to=blake1024@gmail.com \
--cc=rminnich@gmail.com \
--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).