Optimization of inlined functions returning Result?

Дата публикации: 06-10-2026 09:59:40

from the json-rust parser.rs:
// There is a lot of macros here! Like, woah! This is mostly due to the fact
// that Rust isn't very cool about optimizing inlined functions that return
// a `Result` type. Since different functions will have different `Result`
// signatures, the `try!` macro will always have to repackage our results.
// With macros those issues don't exist, the macro will return an unpackaged
// result - whatever it is - and if we ever stumble upon the error, we can
// return an `Err` without worrying about the exact signature of `Result`.
//
// This makes for some ugly code, but it is faster. Hopefully in the future
// with MIR support the compiler will get smarter about this.
how true is this still?
3 posts - 3 participants
Read full topic

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Limitations of `min_specialization` when specializing a generic implementation?	0	9.38	04-10-2026
2	Rust Derive Macros: Why the Compiler Automatically Inlines Them	0	9.29	07-10-2026
3	Type erasure and dyn lifetime in a NonNull/Box struct field	0	8.55	04-10-2026
4	Why no Dependent Matrix Type?	0	5.16	08-10-2026
5	Strategies for dyn trait objects with optional behavior?	0	7.12	06-10-2026
6	Calling static C++ method from Rust	0	9.94	04-10-2026
7	Why is f32/f64::sqrt not const?	0	22.72	06-10-2026
8	Does my lockfree stack impl look correct?	0	6.06	05-10-2026
9	Array initialization post declaration	0	16.79	06-10-2026
10	Trait object with associated types in field - requires generic param?	0	11.08	07-10-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 7.36. Источник: users.rust-lang.org.