Struct muoxi_staging::prelude::CmdSet

pub struct CmdSet {
    pub cmds: Vec<Box<dyn Command + Send>>,
}

Defines a common collection of commands

The current set up for this logic is that CmdSet is a vector of mutable references to trait objects meaning that all commands and their nature must be defined within the Command trait, defining other data associated with the struct of the Command is futile as the compiler will ambiguous to the actual object the trait is attached too. For example:

Example

struct CmdLook
impl CmdLook{
    fn method(){
        println!("Hello from object specific method");
    }
}
impl Command for CmdLoop{
    fn name() -> str{
        "look"
    }
    ...
}

let cmdlook = CmdLook{other: 1};
let cmdset = cmdset![cmdlook];
let cmd = cmdset.get("look").unwrap();

cmd.name(); //valid because this method is defined in trait
cmd.method() // invalid! Method returns object specific method which is invisible.

The main take away from this, is that Commands should run and be defined all within the Trait, creating a unit struct is just to give the Command a name.

Fields

cmds: Vec<Box<dyn Command + Send>>

holds a list of valid commands in set

Methods

impl CmdSet

pub fn new(cmds: Vec<Box<dyn Command + Send>>) -> Self

create a new command set based on appropriate structs that implement Command Trait

pub fn get(&mut self, cmd_string: String) -> Option<&mut (dyn Command + Send)>

check to see if command exists within CmdSet and returns the dyn Command that it matches with this is still fucking confusing

Trait Implementations

impl Debug for CmdSet

fn fmt(&self, f: &mut Formatter) -> Result

Formats the value using the given formatter.