




















































. So if the best things have problems why do invent new things which are easier to grasp at first but got more problems? Maybe it's because we want ppl to use smt that will not inovate things. (btw do not take this serious I just typed a word which would make sense after the previous with the context.) (edited)

. So if the best things have problems why do invent new things which are easier to grasp at first but got more problems? Maybe it's because we want ppl to use smt that will not inovate things. (btw do not take this serious I just typed a word which would make sense after the previous with the context.) (edited)
I just typed a word which would make sense after the previous with the context. worked



























































if (a > 0) { ... } else if (a < 0) instead of use std::signs; match signs::of(num) signs::Positive: ... signs::Negative: ...





if (a > 0) { ... } else if (a < 0) instead of use std::signs; match signs::of(num) signs::Positive: ... signs::Negative: ... 





























































































defer free(a); in C






























open(2) function e.g.
openat



open(2)'s model is enough for many cases. Knowing all the details isn't something very practical.



open(2)'s model is enough for many cases. Knowing all the details isn't something very practical. 


File is less of an abstraction than C's FILE *


open(2) existed already because of historical reasons?, so even if under the hood things changed, open(2) is still useful.
open(2) still exists
openat(2) is available.
open still existsopen anymore

File is less of an abstraction than C's FILE * 

FILE * has bufferingFile is just a file descriptor
open(2)'s manual fit's the programmer needs, then what it does in detail is not important imo.
File is literally 4 byte in size on linux)

open(2)'s manual fit's the programmer needs, then what it does in detail is not important imo. open syscall then, thoughFile::open function in rust

FILE * has buffering 


FILE * is buffered in all libcs that I know







BufReader








BufReader, 5,6,7,8,9 is not done in rust, 10 is guaranteed by rust's guarantees








FILE *?
File you almost always want a bufreader or bufwriter


BufReader, it's still thinner than C's stuff

BufReader, it's still thinner than C's stuff 










char * can refer to a pointer to a char or to such a C string, or to a pointer to a char array, even (edited)








BufReader, it's still thinner than C's stuff 



















1


























































































































4




























































m_FreezeStart and m_FreezeEnd for each tee (character)







TeamMask() to TeamMask(int Team) so you can get the mask for each team separately (and adjust the rest of the code accordingly)

1

60807b5 Fix io_skip return type and documentation - Robyt3
6951795 Add title to engine warnings and make auto-hiding optional - Robyt3
92e2e17 Validate ticks when reading demo chunk headers - Robyt3
0e4f174 Check for all file errors in demo player, show demo error popup - Robyt3
5987d8d Merge pull request #7358 from Robyt3/Engine-Demo-Validation - def-