In no way is it even in the same universe as something that actually accurately measures the specific number of "unsafe expressions" in a crate. log.txt in the root directory of a crate.įor example, a binary crate written like so: fn main() that closes it". I'd tend to argue that (in general, putting actix entirely aside) cargo-geiger is nothing more than a primitive word counting utility that provides output less useful than what you'd get from, say, running rg unsafe.
awc: one unsafe fn without any local uses. actix-service: some unsafe code, but cargo-geiger reports that it's not used in the build (likely disabled by a feature). actix-codec: cargo-geiger shows 10 unsafe expressions but I can't see them in actix git, might be a bug. actix-router: 1 unsafe block, commented. Judging by this comment from one of the Actix org members, a PR with comments explaining why they're sound and/or debug assertions would be appreciated. actix-utils: 9 unsafe blocks, no comments on why they're sound. (Some of the benchmarking code looks sketchy, but who cares - it's not in the build anyway). actix-http: 13 unsafe blocks, all are commented and look reasonable at a glance. Many actix-* crates don't use any unsafe code at all! Here are the ones that do: In the interest of transparency (and to curb speculation), I've created a hello-world project, made it depend on actix-web 3.0.0 with default features and ran cargo geiger on it. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. 
For content that does not, use a text post to explain its relevance. Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. Strive to treat others with respect, patience, kindness, and empathy. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity.
0 kommentar(er)
