IO_NEWLINE
or just always use \n
for the JSON writer? Should I add another constant #define JSON_NEWLINE "\n"
then or use the literal "\n"
everywhere in the tests? https://github.com/ddnet/ddnet/pull/6874#pullrequestreview-1544214616IO_NEWLINE
or just always use \n
for the JSON writer? Should I add another constant #define JSON_NEWLINE "\n"
then or use the literal "\n"
everywhere in the tests? https://github.com/ddnet/ddnet/pull/6874#pullrequestreview-1544214616 IO_NEWLINE
would be good. don't add another constant for JSON_NEWLINE
, but directly use \n
everywhereIO_NEWLINE
to avoid the duplicate testing code, but only using \n
also worksCPU vulnerabilities found in the past few years:
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)
https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)
https://aepicleak.com/
https://en.wikipedia.org/wiki/Software_Guard_Extensions#SGAxe
https://en.wikipedia.org/wiki/Software_Guard_Extensions#LVI
https://en.wikipedia.org/wiki/Software_Guard_Extensions#Plundervolt
https://en.wikipedia.org/wiki/Software_Guard_Extensions#MicroScope_replay_attack
https://en.wikipedia.org/wiki/Software_Guard_Extensions#Enclave_attack
https://en.wikipedia.org/wiki/Software_Guard_Extensions#Prime+Probe_attack
https://www.vusec.net/projects/crosstalk/
https://en.wikipedia.org/wiki/Hertzbleed
https://www.securityweek.com/amd-processors-expose-sensitive-data-new-squip-attack/
int GameFlags = 0;
, check whether the client was redirected already and ignore the packet in that caseDelClientCallback
instead of bloating in a new ignore message concepttvb_memcpy(src, dst, offset, len)
(edited)memcpy
function?count * size_of::()
bytes from src
to dst
. The source and destination must not overlap.pub const unsafe fn copy_nonoverlapping<T>(
src: *const T,
dst: *mut T,
count: usize
)
(edited)memcpy
memcpy
* "testy, virtual(-izable) buffer". They are testy in that they get mad when
* an attempt is made to access data beyond the bounds of their array. In that
* case, they throw an exception.
ptr::copy_nonoverlapping
vs ptr::copy
sort_unstable
vs sort
[]
vs unchecked_get
unreachble!
vs unreachable_unchecked
[]
vs get
is a place where the shorter option isn't the one poviding more guaranteesd8c0511
Add constructor for CSetting
and use emplace_back
- Robyt3
b412153
Ignore listbox hotkeys when modifier, shift or alt pressed - Robyt3
177f748
Render editor status bar except tooltip behind popups - Robyt3
71500fd
Improve server settings editor and status bar - Robyt3
b70b162
Merge pull request #6915 from Robyt3/Editor-Server-Settings-Improvements - heinrich5991fn swap<T>(vec: Vec<(T, T)>) -> Vec<(T, T)> {
vec.into_iter().map(|(x, y)| (y, x)).collect()
}
(edited)