Oh my bad, I read that as nullptr, I use a custom optional that does not support such a silly mode as "disengaged"
That is actually memory safe, as null will always trigger access violation.. Anyway safety checked modes are sufficient for many programs, this article claims otherwise but then contradicts itself by showing that they…
Error Log/assertions prints are by are the most likely code to have not been run prior. Some compilers type check printf, but not all.
Good article, but for profiling you are missing the big daddy of them all, Tracy.
My understanding is Rust compiles each crate in the same way C++ compiles each .cpp file, so if you stick everything in a single crate you get horrible compile times. This does seem like a poor design decision by Rust…
The android team wasn't comparing like to like, though people seem to gotten the impression they were.
OpenAI appears to have bought the DRAM, not to use it, as they are apparently buying it in unfinished form, but explicitly to take it off the market and cause this massive price increase & squash competition. I would…
One other accident that was similiar, but these planes have had a ton of crashes for other reason.
The python example looks fixable with a reentrant mutex, no idea if that translates to the Rust issue.
Ya ever heard of this thing called a debugger? They have this amazing ability to show you what the problem is right when it happens!
So you have to write fugly code just to get something that should be a compiler switch?
Does it work with large binary files and not choke like git? Cause git may have won for webdev etc, but in some industries such as gamedev, Perforce is the king... git is barely used at all because it can't handle…
I dunno, the C++ template implementation of this macro would be far easier to read as it is just normal C++.
Article doesn't make much sense, rambles on about frame stacks and calling convention etc, when these don't matter very much on modern hardware, and are hardly standardized(windows and linux don't use the same CC).…
Somewhat interesting read, if rather long.. My experience is that multi-threading has quite abit of overhead, not necessary from the scheduling, but from the cache misses because now everything is unlikely to be in…
Reserve(reserve_exact in rust lingo) as a concept doesn't throw away amortized growth promise, so this entire post makes no sense. You would need a very shitty implementation to achieve anything close to what you are…
8 bit is not absent in x86 SIMD, it is a slightly less covered than 32 & 16 bit, but you can fully implement all the common 8 bit ops and most are 1 instruction(with AVX2). There are even various horizontal ops on 8 bit…
The slowdown can be enormous if you use SIMD, I believe MSVC emits a write to memory after every single SIMD op in debug, thus the code is incredibly slow(more than 10x). If you have any SIMD kernels you will suffer,…
They never mention std::weak_ptr which makes me think they aren't aware of it.. yes this looks pretty useless and unsafe(isn't everything multi-threaded these days..)
Mobile games are 99% shovelware
You should see the C++ threads
No it isn't, I grew up in NorCal with earthquakes, a 4.6 is a complete nothing burger, you shrug and continue about your day.
std::array [] is checked if you have the appropriate build settings toggled, which of course you should during development. The same applies to many of the other baseless complaints I'm seeing here, learn to use your…
Maybe x86 should add a flag to toggle the weaker memory model on
Is there a C++ port of ipnsort?
Oh my bad, I read that as nullptr, I use a custom optional that does not support such a silly mode as "disengaged"
That is actually memory safe, as null will always trigger access violation.. Anyway safety checked modes are sufficient for many programs, this article claims otherwise but then contradicts itself by showing that they…
Error Log/assertions prints are by are the most likely code to have not been run prior. Some compilers type check printf, but not all.
Good article, but for profiling you are missing the big daddy of them all, Tracy.
My understanding is Rust compiles each crate in the same way C++ compiles each .cpp file, so if you stick everything in a single crate you get horrible compile times. This does seem like a poor design decision by Rust…
The android team wasn't comparing like to like, though people seem to gotten the impression they were.
OpenAI appears to have bought the DRAM, not to use it, as they are apparently buying it in unfinished form, but explicitly to take it off the market and cause this massive price increase & squash competition. I would…
One other accident that was similiar, but these planes have had a ton of crashes for other reason.
The python example looks fixable with a reentrant mutex, no idea if that translates to the Rust issue.
Ya ever heard of this thing called a debugger? They have this amazing ability to show you what the problem is right when it happens!
So you have to write fugly code just to get something that should be a compiler switch?
Does it work with large binary files and not choke like git? Cause git may have won for webdev etc, but in some industries such as gamedev, Perforce is the king... git is barely used at all because it can't handle…
I dunno, the C++ template implementation of this macro would be far easier to read as it is just normal C++.
Article doesn't make much sense, rambles on about frame stacks and calling convention etc, when these don't matter very much on modern hardware, and are hardly standardized(windows and linux don't use the same CC).…
Somewhat interesting read, if rather long.. My experience is that multi-threading has quite abit of overhead, not necessary from the scheduling, but from the cache misses because now everything is unlikely to be in…
Reserve(reserve_exact in rust lingo) as a concept doesn't throw away amortized growth promise, so this entire post makes no sense. You would need a very shitty implementation to achieve anything close to what you are…
8 bit is not absent in x86 SIMD, it is a slightly less covered than 32 & 16 bit, but you can fully implement all the common 8 bit ops and most are 1 instruction(with AVX2). There are even various horizontal ops on 8 bit…
The slowdown can be enormous if you use SIMD, I believe MSVC emits a write to memory after every single SIMD op in debug, thus the code is incredibly slow(more than 10x). If you have any SIMD kernels you will suffer,…
They never mention std::weak_ptr which makes me think they aren't aware of it.. yes this looks pretty useless and unsafe(isn't everything multi-threaded these days..)
Mobile games are 99% shovelware
You should see the C++ threads
No it isn't, I grew up in NorCal with earthquakes, a 4.6 is a complete nothing burger, you shrug and continue about your day.
std::array [] is checked if you have the appropriate build settings toggled, which of course you should during development. The same applies to many of the other baseless complaints I'm seeing here, learn to use your…
Maybe x86 should add a flag to toggle the weaker memory model on
Is there a C++ port of ipnsort?