s_ not m_. m_ is reserved for member variables of a class or struct. The two variables m_Verified and m_VerifyTries should be member variables of the class CMenus in this case. the output ofpGet->Result(cChar, cSize); is never used anywhere and you don't actually need the result so just remove that. (You can also look at CHttpRequest::Results intended usage if you want to since how you use it is not correct, you can find an example here: https://github.com/ddnet/ddnet/blob/9be9a902e7f3e9cd5418823ef88b70e32dd797af/src/engine/shared/http.cpp#L427-L433.). A return statement is not necessary at the end a void type function. Also move auto Time = std::chrono::duration_cast<std::chrono::milliseconds>(time_get_nanoseconds() - StartTime); into the else block and mark it const since it is never modified and is not used outside of the else block. Don't forget to format your code with something like clang-tidy and squash your commits. maybe i missed some things or said smth wrong, correct me if so 
s_ not m_. m_ is reserved for member variables of a class or struct. The two variables m_Verified and m_VerifyTries should be member variables of the class CMenus in this case. the output ofpGet->Result(cChar, cSize); is never used anywhere and you don't actually need the result so just remove that. (You can also look at CHttpRequest::Results intended usage if you want to since how you use it is not correct, you can find an example here: https://github.com/ddnet/ddnet/blob/9be9a902e7f3e9cd5418823ef88b70e32dd797af/src/engine/shared/http.cpp#L427-L433.). A return statement is not necessary at the end a void type function. Also move auto Time = std::chrono::duration_cast<std::chrono::milliseconds>(time_get_nanoseconds() - StartTime); into the else block and mark it const since it is never modified and is not used outside of the else block. Don't forget to format your code with something like clang-tidy and squash your commits. maybe i missed some things or said smth wrong, correct me if so 
2
on my way to becoming godot contributors 
1
1 
pub trait ArchitectureClone {
fn clone_box(&self) -> Arch;
}
pub trait Architecture: ArchitectureClone {
...
}
pub type Arch = Box<dyn Architecture>;
impl<T> ArchitectureClone for T
where
T: 'static + Architecture + Clone,
{
fn clone_box(&self) -> Arch {
Box::new(self.clone())
}
}
impl Clone for Arch {
fn clone(&self) -> Self {
self.clone_box()
}
}
the most "advanced" rust code I've written so far just to be able to clone trait object r7 register 
pub trait ArchitectureClone {
fn clone_box(&self) -> Arch;
}
pub trait Architecture: ArchitectureClone {
...
}
pub type Arch = Box<dyn Architecture>;
impl<T> ArchitectureClone for T
where
T: 'static + Architecture + Clone,
{
fn clone_box(&self) -> Arch {
Box::new(self.clone())
}
}
impl Clone for Arch {
fn clone(&self) -> Self {
self.clone_box()
}
}
the most "advanced" rust code I've written so far just to be able to clone trait object Arc<dyn Architecture> insteadArc<dyn Architecture> instead Rc, my program is not multi threaded.clone() Rc<> is usually preferable
I just wanna make a fancy ahh bind menu
I just wanna make a fancy ahh bind menu 
1
fn main() {
let val = Rc::new(0x45u8);
foo(val.clone());
}
fn foo(mut r: Rc<u8>) {
Rc::get_mut(&mut r); // can
r.get_mut(); // cant
} 
for the love of god someone teach me rust already. my brain is not working just reading the book. for the love of god someone teach me rust already. my brain is not working just reading the book. for the love of god someone teach me rust already. my brain is not working just reading the book. for the love of god someone teach me rust already. my brain is not working just reading the book. if nintendo games has ACE in it does that means they are bad at security too
&mut Rc<T> as an argument, not &mut self 
Rc::get_mut 
Rc was the wrong suggestion to you. I thought dyn Architecture doesn't change after it was created? &mut self, because it has buffer which it writes generated code to 
1 win-win win-win so you can just create unsafe pointer for specific purposes? what i'm thinking is there are some virutal chips that read/writes a set region of memory for specific purposes, like a controller writing state in a region, a PPU/GPU that reads in another region. Then run a wasm in that fixed memory space along with those two piece of real-time code ("virtual chip lmao"), and you have a game console well i guess for performace it would be better if the first three is the same wasm, but again, i think a wasm binary could just be a game rom.
1
null sometimes, idk when 
try_into/try_from or into/from as appropriate as eventually. I hope rust does thatas eventually. I hope rust does that 
1.at() vs [] as could also just panic if type doesnt match
bcs index out of bounds does that too[] for the non-UB variant as could also just panic if type doesnt match
bcs index out of bounds does that too as does, so it should probably not change semanticsas does, so it should probably not change semantics 
std::filesystem being UB
///) 
1char in type char***? char is the pointee type of char * maybe