Struct DirectorySetting

pub struct DirectorySetting {
    pub meta: GameSettingMeta,
    /* private fields */
}

Fields

meta: GameSettingMeta

Implementations

impl DirectorySetting

Refactor to clone less shit Use std::mem::take for the comment and change parse_data_directory to accept &str

pub fn new<S: Into<String>>( value: S, source_config: PathBuf, comment: &mut String, ) -> Self

pub fn original(&self) -> &String

pub fn parsed(&self) -> &PathBuf

Trait Implementations

impl Clone for DirectorySetting

fn clone(&self) -> DirectorySetting

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DirectorySetting

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

Formats the value using the given formatter.

impl Display for DirectorySetting

This is tricky. The trait implementation for GameSetting necessitates that all settings have a Display method. However, DirectorySetting is reused interchangeably amongst variants that use a different key. So really the key should just be skipped here, And handled by the upper SettingValue implementation? But that, also, is fucked off, because then we wouldn’t be able to handle comments. So the hope I guess is that the SettingValue itself can have an implementation to account for this. That seems fair? And then we just assume data= is the default in here.

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

Formats the value using the given formatter.