Why does removing return give me an error: expected type `()` but found type

by

Rust is expression-oriented. In any block, the last expression inside it is the value of the block. Thus, for a function, the last value in the block is treated as a return value.

In other blocks, though, this is not the case—the last value is, after all, treated as the value of the block, not as a return value for the function.

Take the snippet in isolation with just a bit added for clarity:

let has_factor = if number % i == 0 && i != number {
    false
}

This means that the outcome of the if statement as a whole is false if the clause is true, and that value is then duly inserted into the has_factor variable. If the clause is not true, then the else clause will be evaluated. Given that there is no else clause, it is as though else { } had been written, which is equivalent to else { () }. This else block evaluates to (), the unit type. Now we have a mismatch: is the if block (and hence the has_factor variable) of the type bool, as the if block requires, or (), as the [lack of] else block requires? This is where the error comes from.

Summary: you can’t just omit the return keyword, because that’s not what the expression orientation means. At the end of a function, they boil down to the same thing and the sans-return form should be preferred, but in other locations they are not equivalent and return must be explicit.

Final code:

fn is_prime(number: i64) -> bool {
    for i in 2..number {
        if number % i == 0 && i != number {
            return false;
        }
    }
    true
}

More Related Contents:

  1. What are Rust’s exact auto-dereferencing rules?
  2. Why is a trait not implemented for a type that clearly has it implemented?
  3. How can I include a module from another file from the same project?
  4. What does “Sized is not implemented” mean?
  5. How do I implement a trait I don’t own for a type I don’t own?
  6. How do I implement Copy and Clone for a type that contains a String (or any type that doesn’t implement Copy)?
  7. What makes something a “trait object”?
  8. Is it possible to use `impl Trait` as a function’s return type in a trait definition?
  9. Cannot borrow as immutable because it is also borrowed as mutable in function arguments
  10. What is the relation between auto-dereferencing and deref coercion?
  11. What is the return type of the indexing operation?
  12. How to do a binary search on a Vec of floats?
  13. Change enum variant while moving the field to the new variant
  14. I implemented a trait for another trait but cannot call methods from both traits
  15. When is it useful to define multiple lifetimes in a struct?
  16. Can I write an Iterator that mutates itself and then yields a reference into itself?
  17. Moved variable still borrowing after calling `drop`?
  18. Is it possible to declare the type of the variable in Rust for loops?
  19. Is there a way to combine multiple traits in order to define a new trait? [duplicate]
  20. How can I store a pattern in a variable in Rust?
  21. How to switch between Rust toolchains?
  22. What does “missing lifetime specifier” mean when storing a &str in a structure?
  23. How do I print an integer in binary with leading zeros?
  24. What does Rust’s unary || (parallel pipe) mean?
  25. How to create and write to memory mapped files?
  26. Downcast traits inside Rc for AST manipulation
  27. Why does Valgrind not detect a memory leak in a Rust program using nightly 1.29.0?
  28. How to check in Rust if architecture is 32 or 64 bit?
  29. What is the null pointer optimization in Rust?
  30. Is there any way to restrict a generic type to one of several types?

Leave a Comment