From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] I've written a filter in Rust
Date: Fri, 28 Feb 2025 17:35:08 +0200
Message-ID: <90C96DE8-EA03-46AE-8307-1B4B79942303@remlab.net> (raw)
In-Reply-To: <20250227210145.GH4991@pb2>
Le 27 février 2025 23:01:45 GMT+02:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
>we have a memleak, a use after free, a aliasing violation,
>some invalid pointer and a out of array read
>
>a safe language should not allow any of this
>C++ allows all of it, its not safe, switching to C++ doesnt help
To be fair, Rust allows memory leaks, though it vastly reduces the situations in which they can happen. And it will compile code attempting out of bounds slice or array accesses (though that code will panic at runtime).
But I agree that C++ isn't worth switching to.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-02-28 15:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:06 Leandro Santiago
2025-02-20 16:20 ` Leandro Santiago
2025-02-20 22:49 ` Michael Niedermayer
2025-02-21 7:56 ` Leandro Santiago
2025-02-21 9:01 ` Tomas Härdin
2025-02-21 9:21 ` Soft Works
2025-02-21 13:21 ` Michael Niedermayer
2025-02-21 14:30 ` Soft Works
2025-02-21 14:53 ` Kieran Kunhya via ffmpeg-devel
2025-02-21 15:02 ` Soft Works
2025-02-21 19:27 ` Kieran Kunhya via ffmpeg-devel
2025-02-21 20:10 ` Soft Works
2025-02-26 13:50 ` Tomas Härdin
2025-02-26 14:18 ` Zhao Zhili
2025-02-26 15:32 ` Rémi Denis-Courmont
2025-02-26 16:03 ` Zhao Zhili
2025-02-26 16:25 ` martin schitter
2025-02-26 14:07 ` Nicolas George
2025-02-26 16:35 ` Soft Works
2025-02-27 22:40 ` Michael Niedermayer
2025-02-21 16:39 ` Stephen Hutchinson
2025-02-26 14:25 ` Vittorio Giovara
2025-02-21 13:18 ` Lynne
2025-02-21 13:44 ` Kieran Kunhya via ffmpeg-devel
2025-02-21 18:02 ` Tomas Härdin
2025-02-22 12:57 ` Rémi Denis-Courmont
2025-02-23 21:30 ` Tomas Härdin
2025-02-23 21:51 ` Michael Niedermayer
2025-02-26 14:11 ` Tomas Härdin
2025-02-27 21:01 ` Michael Niedermayer
2025-02-28 1:57 ` Pavel Koshevoy
2025-02-28 15:35 ` Rémi Denis-Courmont [this message]
2025-02-24 14:51 ` Rémi Denis-Courmont
2025-02-26 14:34 ` Tomas Härdin
2025-02-26 15:13 ` Leandro Santiago
2025-02-22 12:49 ` Rémi Denis-Courmont
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=90C96DE8-EA03-46AE-8307-1B4B79942303@remlab.net \
--to=remi@remlab.net \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git