内容简介:Rust has two major mechanisms for delegating logic: enums and trait objects, and it may be unclear when to use one or the other. In this post, I will walk through how each works, what the tradeoffs are, and how to choose the right option for your code.An e
Rust has two major mechanisms for delegating logic: enums and trait objects, and it may be unclear when to use one or the other. In this post, I will walk through how each works, what the tradeoffs are, and how to choose the right option for your code.
Enums: Closed Set of Types
An enum, or enumeration is a type which can be one of several distinct variants , each possibility containing some addition data. Enums are one of Rust’s core data types, can look like any of the following, as examples:
enum Option<T> { Some(T), None, } enum Result<T, E> { Ok(T), Err(E), } enum IpAddress { V4(u8, u8, u8, u8), V6(String), }
Note that enums are, by their nature, a closed set of types . You define a finite list of variants, and those are the only ones which can exist. In the future, you can add variants yourself by modifying the definition of the enum type (and possibly changing call sites / users of the enum to handle the additional variant), but users of your enum type can’t add additional variants themselves.
The advantage of enums is that they are fast. Because the total list of variants is known at compile-time, selection of what code to execute based on the variant at hand is only a branch instruction.
Trait Objects: Open Set of Types
Trait Objects allow for the uniform treatment of different concrete types which all implement the same trait, like so:
use std::f64::consts::PI; /// Defines how to get the area of a shape. trait Area { fn area(&self) -> f64; } /// A rectangular shape with a width and height. struct Rectangle { width: f64, height: f64, } impl Area for Rectangle { // Area for a rectangle is width times height. fn area(&self) -> f64 { self.width * self.height } } /// A circular shape with a radius. struct Circle { radius: f64, } impl Area for Circle { // Area for a circle is PI * r^2 fn area(&self) -> f64 { PI * self.radius * self.radius } } fn main() { // Make a `Vec` that holds trait objects based on the `Area` // trait. This lets the `Vec` hold different concrete types // by putting them behind a pointer, which hides what type // is actually there, and dispatches to the correct method // implementations at runtime! let shapes: Vec<Box<dyn Area>> = vec![ Box::new(Rectangle { width: 2.0, height: 3.0 }), Box::new(Circle { radius: 4.0 }) ]; for shape in &shapes { println!("{}", shape.area()); } }
By contrast, a trait object is an open set of types . Trait objects are Rust’s key mechanism for dynamic dispatch, allowing selection at runtime at which concrete type’s trait method implementation should be executed.
This dynamic dispatch does come with a cost, as the vtable must be checked to determine the location of the appropriate instructions to execute.
The advantage with trait objects is that users can define their own types which implement the trait, and can then be used wherever a trait object is expected.
Note as well that trait objects may be represented as Box<dyn Trait>
(an owned trait object), or
as &dyn Trait
or &mut dyn Trait
(borrowed trait objects). In either case, they represent an
open set of types which uses dynamic dispatch for method execution.
Summarizing Trade-Offs
Delegation Construct | Set of Types | Performance | Restrictions |
---|---|---|---|
Enum | Closed | Fast (branch) | N/A |
Trait Object | Open | Slow (vtable) | Object Safety |
When to Use Them?
With the trade-offs understood, the question is when to use one or the other. This is going to be dependent on your context.
In general, if the need for delegation is only internal, meaning you control all the variants which may at some point need to be constructed in the future, you’re likely better off with an enum. It’s faster, subject to fewer rules (no “object safety” equivalent), and makes it easy to see a list of all the variants which may exist.
If the need for delegation is exposed externally, and you want to be maximally flexible for users of your crate, then a trait object is the better option. While you pay a performance cost for the dynamic dispatch, the flexibility gained is sometimes irreplaceable.
以上所述就是小编给大家介绍的《Enum or Trait Object》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
集创思维设计矩阵
慈思远 / 电子工业出版社 / 2017-4 / 72.00元
《集创思维设计矩阵——写给互联网人的设计指南》总结了作者从业7年以来的设计经历,在大量企业所面对的设计问题基础上,提出了枪型思维,即如何给产品更准确的定位。 在定位准确的基础上加以设计,提出了设计中高维度融合低维度的设计思维,即设计者可以从商业逻辑推演到设计逻辑,让设计更加精确;又提出了设计和计算的博弈,指出在每一步创新的基础上,设计者一定要清晰地评判设计的代价。这样设计后的产品才是可以和企......一起来看看 《集创思维设计矩阵》 这本书的介绍吧!