演讲者可能会提及其他内容：

• Rust’s type system borrows a lot of ideas from functional programming languages.

  For example, Rust’s enums are known as “algebraic data types” in languages like Haskell and OCaml. You can take inspiration from learning material geared towards functional languages when looking for guidance on how to design with types. “Domain Modeling Made Functional” is a great resource on the topic, with examples written in F#.

• Despite Rust’s functional roots, not all functional design patterns can be easily translated to Rust.

  For example, you must have a solid grasp on a broad selection of advanced topics to design APIs that leverage higher-order functions and higher-kinded types in Rust.

  Evaluate, on a case-by-case basis, whether a more imperative approach may be easier to implement. Consider using in-place mutation, relying on Rust’s borrow-checker and type system to control what can be mutated, and where.

• The same caution should be applied to object-oriented design patterns. Rust doesn’t support inheritance, and object decomposition should take into account the constraints introduced by the borrow checker.

• Mention that type-level programming can be often used to create “zero-cost abstractions”, although the label can be misleading: the impact on compile times and code complexity may be significant.