Viewing profile — Measter

In terms of "finished" projects, I wrote a program that generated new, empty, histories for Crusader Kings II. It could create new cultures, religions, and titles, and did a simple…

They're a long-time anti-Rust zealot. This is the sort of nonsense they've been coming out with for years.

Which is probably a case of the human prompting the AI only being able to see the decoy message, so they think the AI was able to read it because it matches what they can see.

There's also the element of actual humans being unable to read the intended message, and only seeing the decoy text. It's a pretty crappy system if a portion of your intended audie…

Complete and utter nonsense. Every Windows tool I remember using has handled LF-only endings perfectly fine, meanwhile Linux tools regularly fail to handle CRLF endings.

The only times I can remember having line-ending issues is using GNU's tools on Linux. Every Windows tool I can remember using accepts both CRLF and LF.

Microsoft's PowerToys did add that in (I think) the last version. Alt + Left click moves, alt + right click resizes.

That's not really that surprising when you think about it. Standard library-provided things are implemented on a basis of working OK for as many scenarios as possible, not on one o…

Hilariously, I had the exact opposite. I use Fira Code, which I eliminated in the first round.

> It's as if someone asked you how many 1s there are in the binary representation of this text. I'm actually kinda pleased with how close I guessed! I estimated 4 set bits per char…

No, it isn't. Because that distinction is significant if you are using the language in an environment where those libraries are not available or suitable, such as the Linux project…

The Rust language has exactly that level of control. Rust's Alloc and STD implementations do not yet provide it.

Memory allocations in Rust are also always done explicitly, but Rust's library types don't have APIs that allow you to get it wrong.

Another issue we have to consider here for the measurements taken then is that it was miscompiling, which, to me, calls into question how much we can trust that performance change.…

> On the other hand, signed integer overflow being UB would count for C/C++ C and C++ don't actually have an advantage here because this is only limited to signed integers unless y…

> In debug mode, rust programs also crash on unsigned integer overflow. All integer overflow, not just unsigned. Similarly, in release mode (by default) all integer overflow is ful…

And, by default, panicking in Rust also doesn't crash, it begins a stack unwind which can be caught on any layer above it with catch_unwind.

Fun fact: that's what an unwrap does. It panics, which causes the error to be logged and the thread ended.

Back in 2015 when the Rust project first had to disable use of LLVM's `noalias` they found that performance dropped by up to 5% (depending on the program). The big caveat here is t…

It's interesting that I've also heard the same from people involved in Rust. Expecting more interest from C++ programmers and being surprised by the numbers of Ruby/Python programm…

For Rust vs C++, I'd say it'll be much easier to have a complete understanding of Rust. C++ is an immensely complex language, with a lot of feature interactions. C# is actually fai…

So in Rust an unsafe block and an unsafe function mean two different things. An unsafe block allows you to do things that are unsafe, such as dereference raw pointers, access union…

A segfault is not the program performing a runtime check and doing a controlled shutdown. A segfault is the OS detecting the program doing something it's not allowed to and killing…

Only if that memory page is unmapped, and only if the optimizer doesn't detect that it's a null pointer and start deleting verification code because derefing null is UB, and UB is …

> Take Herb Sutter for example, who argues that "memory safety" as defined in this article is an extreme goal and we should instead focus on a more achievable 95% safety instead to…