Measter

11 ms·

1.
by Measter 12d ago
A project I've just started is to follow the Roguelikedev tutorial on a 32-year-old PC, using the period dev tools. I'm going to have to write everything myself, and I'm currently researching how to poke the graphics adaptor.
2.
by Measter 24d ago
Yup, definitely the Rust users who are toxic. Totally not the people going into every thread about Rust to tell everyone about how toxic Rust users are. Nope.
3.
by Measter 1mo ago
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 simulation of them spreading over the map. I also
4.
by Measter 2mo ago
They're a long-time anti-Rust zealot. This is the sort of nonsense they've been coming out with for years.
5.
by Measter 2mo ago
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.
6.
by Measter 2mo ago
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 audience can't even read it.
7.
by Measter 4mo ago
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.
8.
by Measter 4mo ago
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.
9.
by Measter 4mo ago
Microsoft's PowerToys did add that in (I think) the last version. Alt + Left click moves, alt + right click resizes.
10.
by Measter 4mo ago
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 of being the best possible implementation for every poss
11.
by Measter 6mo ago
Hilariously, I had the exact opposite. I use Fira Code, which I eliminated in the first round.
12.
by Measter 6mo ago
> 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 character, which with 491 characters in your post (
13.
by Measter 8mo ago
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 which uses a custom fork of Alloc which provides colle
14.
by Measter 8mo ago
The Rust language has exactly that level of control. Rust's Alloc and STD implementations do not yet provide it.
15.
by Measter 8mo ago
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.
16.
by Measter 8mo ago
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. Additionally, it was 10 years ago and LLVM has changed. It
17.
by Measter 8mo ago
> 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 you use compiler-specific intrinsics. Rust'
18.
by Measter 9mo ago
> 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 fully defined as two's complement wrap.
19.
by Measter 10mo ago
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.
20.
by Measter 10mo ago
Fun fact: that's what an unwrap does. It panics, which causes the error to be logged and the thread ended.
21.
by Measter 10mo ago
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 that it was miscompiling, so some of that apparent perfo
22.
by Measter 10mo ago
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 programmers interested. I wonder if it's that Ru
23.
by Measter 10mo ago
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 fairly complex. I'm not sure if it's quite
24.
by Measter 10mo ago
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 fields, calling unsafe functions, etc. Unsafe functions mar
25.
by Measter 10mo ago
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 it.
26.
by Measter 10mo ago
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 assumed to never happen.
27.
by Measter 10mo ago
> 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 spend the remaining effort on other types of s
28.
by Measter 10mo ago
There are also limits to what the borrow checker is capable of verifying. There will always be programs which are valid under the rules the borrow checker is enforcing, but the borrow checker rejects. It's kinda annoying when you run i
29.
by Measter 11mo ago
That support could be Microsoft driven. Parts of Windows 11 are written in Rust, and having that platform in Tier 1 makes their lives easier.
30.
by Measter 11mo ago
There's no push to add Debian's officially supported platforms to Rust because Rust already supports those platforms.

More ›