1
2
3
5
good morning btw
1 good morning btw 
1
1
):
1. rm -Force build
2. mkdir build
3. cd build
4. cmake ..
5. cmake --build . -j
6. cd debug
7. mv .\steam_api.dll .\DDNet.exe ..
I think there is a lot of "unnecessary" stuff happening. someone told me a better way to build, although I forgot. Can someone maybe point out a better way to build? 
1):
1. rm -Force build
2. mkdir build
3. cd build
4. cmake ..
5. cmake --build . -j
6. cd debug
7. mv .\steam_api.dll .\DDNet.exe ..
I think there is a lot of "unnecessary" stuff happening. someone told me a better way to build, although I forgot. Can someone maybe point out a better way to build? cmake --build . -j works exactly. Does it overwrite changes making the rm unnecessary? cmake --build should only recompile necessary changes. rm shouldn't be necessary
1--clean-first if you want a.. well.. clean rebuild 1 1 1cmake .. and cmake --build . -j 1
1
1spectate_free_view and spectate_recent to the Spectate-Mode
spectate_free_view: changes to Free View
spectate_recent: Spectates the most recently spectated player spectate -1 for Free View I didnt know until i looked in the code tho. maybe adding it to the command description would help some 
as all things should be
3
2#[derive(Debug, Clone, PartialEq)]
pub struct ExprStruct {
name: String,
fields: BTreeMap<String, Expr>,
}
impl IntoIterator for ExprStruct {
type Item = (String, Expr);
type IntoIter = <BTreeMap<String, Expr> as IntoIterator>::IntoIter;
fn into_iter(self) -> Self::IntoIter {
self.fields.into_iter()
}
}
is this a cursed way to implement .into_iter() or is it ok? <BTreeMap<String, Expr> as IntoIterator>::IntoIter part, maybe it's bad ¯\_(ツ)_/¯
1<BTreeMap<String, Expr> as IntoIterator>::IntoIter part, maybe it's bad ¯\_(ツ)_/¯ btree_map::IntoIter<String, Expr>btree_map::IntoIter<String, Expr> 
#[derive(Debug, Clone, PartialEq)]
pub struct ExprStruct {
name: String,
fields: BTreeMap<String, Expr>,
}
impl IntoIterator for ExprStruct {
type Item = (String, Expr);
type IntoIter = <BTreeMap<String, Expr> as IntoIterator>::IntoIter;
fn into_iter(self) -> Self::IntoIter {
self.fields.into_iter()
}
}
is this a cursed way to implement .into_iter() or is it ok? 