DLoupe

5 ms·

1.
by DLoupe 10mo ago
I think you missed my point. The problem is not lack of guarding against programmer mistakes. It's that the compiler generates unnecessary code.
2.
by DLoupe 10mo ago
"Another difference in Rust is that values cannot be used after a move, while they simply "should not be used, mostly" in C++" That's one of my biggest issues with C++ today. Objects that can be moved must support a
3.
by DLoupe 1y ago
and of Even Toned Screens, the halftoning algorithm used by many linux print drivers.
4.
by DLoupe 1y ago
The compiler generates code for calling the destructor after the object was moved. This was problem #1. Regarding #2, take Resource Acquisition Is Initialization (RAII) as an example - in RAII, the existence of an object implies the existen
5.
by DLoupe 1y ago
> I wonder what you are doing to get yourself in that situation. The problem with the current move semantics is that, compared to e.g. Rust: 1) the compiler generates unnecessary code and 2) instead of just implementing class T you must
6.
by DLoupe 1y ago
By adding syntax and semantics for destructible moves, meaning the moved object is removed from its scope (without calling its destructor.)
7.
by DLoupe 1y ago
Since I use move semantics all the time, this is for me the most frustrating thing about C++ full stop. I really wish they'd fix this instead of adding all those compile-time features.
8.
by DLoupe 1y ago
For example, boost library's "describe" and similar macro based solutions. Been using this for many years.
9.
by DLoupe 1y ago
If you use Google to backup your WhatsApp chats (most people do), Google can already read your messages, because the backup is not encrypted.
10.
by DLoupe 1y ago
It's called "dynamic pricing" and it's everywhere. https://de.wikipedia.org/wiki/Dynamic_Pricing
11.
by DLoupe 1y ago
Thanks so much for replying, Walter. I'll give it another try.
12.
by DLoupe 1y ago
For me, D failed to replace C++ because of lack of design. It is more a mix of great features. But once you start learning the details simple things can get very complicated. For example, function arguments can be "in", "out&
13.
by DLoupe 1y ago
Its's Evil (Evil = Incompetence + Power)
14.
by DLoupe 2y ago
Why $6,2999 when the article says he payed around $900?
15.
by DLoupe 2y ago
> The safety checks have uncovered over 1,000 bugs In most implementations of the standard library, safety checks can be enabled with a simple #define. In some, it's the default behavior in DEBUG mode. I wonder what this library imp
16.
by DLoupe 2y ago
The chats are encrypted but the backup saved in the cloud isn't. So if someone gets access to your Google Drive he can read your WhatsApp chats. You can opt-in to encrypt the backup but it doesn't work well.
17.
by DLoupe 2y ago
Oops, he did it again. Congrats Raph, and thanks - your work and your writing have been an inspiration to me for my entire career (~25 years).