A Mir Formality Walkthrough 2022-04-20

Rust

Get a comprehensive overview of the Mir Formality Walkthrough, including naming conventions, crate item declarations, and the role of the `copy` keyword in this Rust testing tool.

Key takeaways

Every variant has a name and the naming convention starts with capital letters
Crate item declarations have their own notation and there are different types of crate items (e.g. impl, trait, struct, etc)
A Mir formality walkthrough is done by running tests and manually going through the code
In Mir formality, it’s possible to use the copy keyword, but it doesn’t automatically mean copying and pasting code
The copy keyword is only used for specific implementations and traits
copy doesn’t inherit from sized
There are several ways to not be doing what you think you’re doing in Mir formality
Mir formality walkthroughs typically involve manually running the tests and checking the results one by one
Racket allows for flexible syntax and doesn’t require parentheses, but it’s possible to use them
The crate declaration follows a specific notation and has its own set of rules
Different crates can have different notations and rules
Mir formality walkthroughs can be used to test crates and generate tests programmatically
Mir formality is a way to model and run tests for Rust code, but it’s not a direct translation of Rust syntax

A Mir Formality Walkthrough 2022-04-20

More talks