Rust Questions from Beginners, Including Me

Have Rust beginner questions? Discord has Rust channels for the help you’re looking for!

Beginners are encouraged to ask questions
We are stocked full of answers. But… some are “no”.

Information overload and I’m still trying to find a bigger project I can work on that interests me. I have the Interpreter to work on still, and that will take some serious work! But I’m also thinking of going back to small systems of my programming past and playing with writing them in Rust. In the meantime, I thought I’d sneak around the Rust #beginners channel on Discord and give everyone a peak at some questions (and hopefully some answers) that beginners are asking about their early Rust code.

I have a [u8; 10] and I have tried to do a .map() on it but I get:

note: the method 'map' exists but the following trait bounds were not satisfied:
   '&mut [u8; 10] : std::iter::Iterator'
   '&mut [u8] : std::iter::Iterator'

Try .iter().map(...) (Or iter_mut based on what you need).

So, I’m assuming this is an example of that (though, with u16 so my sum doesn’t get too big):

fn main() {
    let list: Vec<u16> = [1,1,2,3,5,8,13,21,34,55].to_vec();
    list.iter().for_each(|n| println!("The next is: {}", n));
    let sum: u16 = list.iter().map(|n| { n }).sum();
    println!("\nSum of list: {}", sum);

Note a few things here. We couldn’t do:
list.iter().map(|n| println!("The next is: {}", n));
and the compiler nicely reminds us why:
note: iterators are lazy and do nothing unless consumed

So, iter().for_each() closure works nicely … or we could have used an old-school for loop over the iter() instead.

What would be the Rust equivalent for this in C:
#define TEST 1

A constant is appropriate for this case, for example:
const TEST: i32 = 1;

Student looking in book for answers to his questions
I. Don’t. See. My. Question. Anywhere!

I went ahead and asked my beginner question from the previous blog post: when implementing a trait for several “related” structs, I can require other traits that I depend on… but I can’t make a field (that all the structs share) a requirement… which prevents me from being able to write a default implementation of a trait – I have to write it individually for each struct… is that “just how it is”?

And I got back a good answer:

struct fields are not part of a trait's interface; traits can be implemented by things other than structs e.g. enums, primitive types, closures, …

you can add a health(&self) -> u8 method on your trait that each struct is required to implement, and then use that in the trait's implementation of cur_health

if you want the trait to advertise that its implementors have a concept of "health" then that's one way to go about it

All of that makes sense… and leads me to slightly change the code, to see how it looks with that idea…

struct Player {
    player_name: String,
    real_name: String,
    level: u8,
    health: u8,

struct Monster {
    name: String,
    subtype: String,
    hit_dice: u8,
    health: u8,

trait Creature {
    fn health(&self) -> u8; 
    fn cur_health(&self) -> String {
        format!("Health: {}",

impl Creature for Player {
    fn health(&self) -> u8 { }
impl Creature for Monster {
    fn health(&self) -> u8 { }

fn main() {
    let player_1 = Player {
        player_name: "Aragorn".to_string(),
        real_name: "Viggo Mortensen".to_string(),
        level: 20,
        health: 120,
    let monster_1 = Monster {
        name: "Orc".to_string(),
        subtype: "Captain".to_string(),
        hit_dice: 7,
        health: 21,

    println!(" Player 1: {}", player_1.cur_health());
    println!("Monster 1: {}", monster_1.cur_health());

Now, health() is a required trait, and not default implemented (since I can’t), but cur_health() to print the string now CAN be defaulted.

So I can implement the simple health() for each struct and let the “fancy” cur_health() default for each struct type. I do think this is an improvement. I’m not sure I’d even implement any of this in this way, but this example is showing me what is possible.

Author: Jeff Culverhouse

I am a remote Sr Software Engineer for, mainly perl. Learning Rust in my spare time. Plus taking classes at James Madison University. Culverhouse - English: from Old English culfrehūs ‘dovecote’, hence a topographic name for someone living near a dovecote, or possibly a metonymic occupational name for the keeper of a dovecote. ISTP, occasionally INTP.

%d bloggers like this: