From: juntz <zjttime@163.com>
To: linux-kernel@vger.kernel.org
Cc: "zjttime@163.com" <zjttime@163.com>
Subject: Question about C/C++ Safety and Kernel Development
Date: Tue, 5 May 2026 23:38:49 +0800 (CST) [thread overview]
Message-ID: <6854977f.36f8.19df8cabe8a.Coremail.zjttime@163.com> (raw)
Subject: Question about C/C++ Safety and Kernel Development
Dear Mr. Torvalds,
As an amateur developer who is familiar with C language and C++ syntax, I have always been curious whether C or C++ could one day achieve the safety guarantees that Rust provides.
I have read about the challenges of kernel development and the recent adoption of Rust in certain areas of the Linux kernel. I understand that in 1992, the Linux project attempted to use C++ for kernel development but ultimately abandoned the idea.
I would like to ask: what are the fundamental technical reasons that prevent C++ from being used in Linux kernel development? Is it related to:
- The complexity of the language features?
- Runtime overhead?
- Or other technical constraints?
Additionally, what is your perspective on whether modern C++ (using a restricted subset without exceptions, RTTI, etc.) could potentially be considered for future kernel development?
Thank you for your time and for your immense contributions to the open-source community.
Best regards,
juntz
reply other threads:[~2026-05-05 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6854977f.36f8.19df8cabe8a.Coremail.zjttime@163.com \
--to=zjttime@163.com \
--cc=linux-kernel@vger.kernel.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