Compare Go's switch with Rust's match on exhaustiveness, fallthrough, and expressions.
Tests grasp of expression vs statement semantics and type safety. Go switch auto-breaks and lacks exhaustiveness; Rust match requires exhaustive patterns, forbids fallthrough, and yields values. Never say Go switch returns a value or Rust match falls through.
Your understanding of statement versus expression control flow and compile-time pattern safety. State that Go switch is a statement with implicit break, no exhaustiveness checking, and no return value; contrast with Rust match, an expression requiring exhaustive patterns, forbidding fallthrough, and yielding a typed value assignable directly to a variable or returned from a function. Claiming Go switch yields a value or that Rust match allows implicit fallthrough like C is a serious misconception.
Read the original → rustwiki.org
- #go
- #rust
- #control-flow
- #pattern-matching
- #language-design
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.