From: Florian Weimer <fweimer@redhat.com>
To: lkcl via Gcc <gcc@gcc.gnu.org>
Cc: lkcl <luke.leighton@gmail.com>
Subject: Re: rust non-free-compatible trademark
Date: Mon, 18 Jul 2022 20:32:25 +0200 [thread overview]
Message-ID: <87wncaw9ty.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPweEDwN_qzA1Ehpqqw5-Vwxr8G5ajY1N4ESt=UFGTK4gDBJ=A@mail.gmail.com> (lkcl via Gcc's message of "Mon, 18 Jul 2022 15:30:55 +0100")
* lkcl via Gcc:
> if the Rust Foundation were to add an extremely simple phrase
>
> "to be able to use the word rust in a distributed compiler your
> modifications must 100% pass the test suite without modifying
> the test suite"
>
> then all the problems and pain goes away.
No. It would actually make matters worse for GCC in this case because
the stated intent is to ship without a borrow checker (“There are no
immediate plans for a borrow checker as this is not required to compile
rust code”, <https://rust-gcc.github.io/>, retrieved 2022-07-18). There
are of course tests for the borrow checker in the Rust test suite, and
those that check for expected compiler errors will fail with GCC.
Thanks,
Florian
next prev parent reply other threads:[~2022-07-18 18:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 15:28 lkcl
2022-07-17 16:25 ` Richard Biener
2022-07-17 16:47 ` lkcl
2022-07-17 18:24 ` Richard Kenner
2022-07-17 18:57 ` Alexandre Oliva
2022-07-17 16:31 ` Mark Wielaard
2022-07-17 17:06 ` lkcl
2022-07-17 17:41 ` Mark Wielaard
2022-07-17 18:11 ` lkcl
2022-07-17 18:29 ` lkcl
2022-07-17 22:59 ` Mark Wielaard
2022-07-17 23:07 ` lkcl
2022-07-17 23:55 ` Richard Kenner
2022-07-17 18:28 ` Richard Kenner
2022-07-17 18:54 ` Alexandre Oliva
2022-07-18 7:09 ` David Brown
2022-07-18 8:07 ` lkcl
2022-07-18 8:50 ` Jonathan Wakely
2022-07-18 9:06 ` lkcl
2022-07-18 14:30 ` lkcl
2022-07-18 17:11 ` Richard Kenner
2022-07-18 17:12 ` Richard Kenner
2022-07-18 18:32 ` Florian Weimer [this message]
2022-07-18 18:43 ` Arthur Cohen
2022-07-19 9:43 ` Florian Weimer
2022-07-18 19:35 ` lkcl
2022-07-18 21:01 ` David Malcolm
2022-07-18 23:09 ` lkcl
2022-07-19 9:27 ` Gabriel Ravier
2022-07-19 10:26 ` lkcl
2022-07-19 10:55 ` Jonathan Wakely
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=87wncaw9ty.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=luke.leighton@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).