kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Manuel Quintero Fonseca <manuel@uas.edu.mx>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Wouldn't Zig be more suitable than rust? In the Linux kernel
Date: Mon, 23 Sep 2024 20:58:07 -0400	[thread overview]
Message-ID: <CAH8yC8mTb7XRBYFGyo8Vo00AhRtb_zVBibm5ha5SpPJhHiZ6GQ@mail.gmail.com> (raw)
In-Reply-To: <CAPegGh-FyJvBUMghuwAP9HSXfmxBL+N_77ubCysYmi==EqDD6Q@mail.gmail.com>

On Mon, Sep 23, 2024 at 5:08 PM Manuel Quintero Fonseca
<manuel@uas.edu.mx> wrote:
>
> The Zig compiler is compatible with C, Zig code is cleaner than Rust,
> and they are both equally secure.
>
> What do you think?

The kernel needs more than Rust's incomplete x86_64 and i686 support.
Rust would actually have to have Tier 1 support for armel, armv7,
aarch64, loongarch64, mips{64}, powerpc{64}, riscv{64}, sparc{64},
s390x, and a wheelbarrow full of other minor architectures. See
<https://doc.rust-lang.org/nightly/rustc/platform-support.html>.

Zig would have to provide similar support.

I don't believe Rust or Zig would be much help at the moment.

Jeff

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2024-09-24  0:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 21:07 Wouldn't Zig be more suitable than rust? In the Linux kernel Manuel Quintero Fonseca
2024-09-24  0:11 ` Joshua Rose
2024-09-24  0:58 ` Jeffrey Walton [this message]
2024-09-27 11:56 ` Richard

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=CAH8yC8mTb7XRBYFGyo8Vo00AhRtb_zVBibm5ha5SpPJhHiZ6GQ@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=manuel@uas.edu.mx \
    /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).