public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/88737] RFE: Track ownership moves Date: Mon, 18 Dec 2023 07:29:59 +0000 [thread overview] Message-ID: <bug-88737-4-9Fs1XQpUHI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- We do now have the analyzer and -Wuse-after-free. I don't think a rust-like borrow checking feature will ever work or is sensible to implement in C. Use rust if you need such a feature. I'm also not sure a "weaker" form of borrow checking is actually useful. That would leave "custom" alloc-free like attributes using the -Wuse-after-free or the corresponding analyzer diagnostics without any other semantic side-effects. Is that what you actually want?
next parent reply other threads:[~2023-12-18 7:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88737-4@http.gcc.gnu.org/bugzilla/> 2023-12-18 7:29 ` rguenth at gcc dot gnu.org [this message] 2023-12-18 7:45 ` uecker at gcc dot gnu.org
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=bug-88737-4-9Fs1XQpUHI@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).