Once again I get foiled by switching languages. :blobcatfacepalm2:
In Javascript, you have to compare strings with ===, not ==, or else you'll run into type coercion problems, because Javascript thinks 1 == "1" is a totally fine thing to be true. (it's not)
But in Kotlin, === compares identity not equality for strings. But in the JVM, string values are aggressively cached, so === actually does what you want most of the time. Unless your strings come from weird places, like JNI code. Then you get awful non-deterministic behavior that's incredibly hard to debug, but it totally goes away when you use the correct comparison operator == for strings.
sigh I'm not really as good at this whole programming thing as I should be by now.
Request for feedback: how would you change this #Rust compiler error? Can you tell what's going on? What the problem is? Do you get a sense of how you might be able to solve it?
Time passes fast as fuck. In my mind it is 1 or 2 years old only 😅. But I started following it a little after they removed the @ symbols I guess.
Well, for me Rihanna and Miley Cyros is extremely new and recent in my head too so... 😅😞. I have no idea what kids listen to these days... But I ramble 🤣
Fresh out the oven, version 0.8.5 of the open source space game #OutFly!
✅ New flashlight
✅ Redesigned HUD, with #Fallout-4-like bars for health/power/O2, and #car-dashboard-like warning lights
✅ New, well-balanced cruising vehicle
✅ Implemented power drain
✅ Much improved texture for #Jupiter
Btw, see how the hat of the #pizza chef doesn't cast a shadow? Because it ain't real! Just an #AR illusion, which you can toggle with <TAB> :)
I’ve been using new shiny languages for a while now. #Rust, #Zig and #Swift in particular.
I love Rust’s tooling, Swift’s syntax, and Zig’s philosophy, but I feel like good old #Cpp is still the goat.
Yeah, the syntax can get out of hand really quickly.
Yeah, the STL is bloated.
Yeah, the tooling ecosystem is a mess.
But at the end of the day, with a good style guide and some discipline, it can check most of my boxes.
But learning new languages is always fun so I’m still doing it 😬
@diyelectromusic, since you're into embedded tech and microcontrollers, you may appreciate this one.
It's a Real-time Operating System kernel I wrote in C and Assembly for AVR chips. My intent was to learn about how operating systems interface with hardware.
I'd like to rewrite it with #Rust and finish the task scheduler.
So now that -Zcheck-cfg is stabilized and enabled by default, there's no way to tell the compiler about custom cfgs other than a build script?
I routinely use a custom cfg for rustdoc so that I can use nightly features when publishing (both with docs.rs and CI). #[cfg(coverage)] is also used in some places.
Apparently spurious warnings are extremely wide-spread, so I'm not clear on why this was stabilized with such a glaring hole in it.
I came across this article the other day, titled “Why Rust cannot replace C++”.
I feel that the author completely fails to understand the opposing argument. The article claims that with “new” C++ features like smart pointers, you can write safe code in C++, therefore Rust is unnecessary.
But I don’t want a language where I can write safe code, I want a language where I must write safe code.
I know that such a file has to exist because emojos.in works correctly for void.rehab but I don't know enough #Rust to figure out where they're getting the path out of the server instance.
I can't deal with languages with optional semicolons! I like languages without semicolons, but when they're optional, especially if they feel "C-like", I always end up adding semicolons to some lines even when I try to write in a semicolon-less style. I'm writing some #kotlin now and I decided to just use semicolons consistently because the alternative is seemingly to use them inconsistently.
Strangely, this isn't an issue I have in #golang. I do have it in #rust however.
After getting the #Commodore#C64 and #C128 running again, the next device to repair is the #C1571.
It had #corrosion and #rust on the main board and the power supply is beyond repairworthiness. I'd replace the latter with a #meanwell RD-35 with 5 and 12 volt output.
One #diode was rusty, a few traces needed #cleaning and five #resistor looked bad. Hope the black hybrid chip is still okay.
Sadly, the lower read head seems to be broken, my work might've been in vain. #floppydrive#retrocomputer
This was tried a couple of years ago, but there some issues with mingw - so kudos to the folks that investigated and fixed those (sorry that I don't have links)!
Next step, the MSVC builders, which will require bumping the version of Clang that's used to build LLVM first...
Yesterday in #LibrePlanet chat I named the #Makepad project, a real adorable 😍 effort that's still lacking on the #a11y side, i.e. could do with some #AccessKit on board.
Today I found out that Makepad is apparently part of a #Rust appdev effort, called #Robius. Another project here is #Dioxus.. also in for @accesskit#accessiblity support.. maybe. 🤔
Robius looks like a very loose conglomeration of independent projects. Maybe AccessKit is even a fit to it?
Thanks so much to everyone who hung in this week as we’ve all worked to fix the state of the Nix community. It’s been a ride; but I think things are going to get better.
Here’s the last major piece of the puzzle — the product of several months of work from an absolutely incredible team. It’s not ready for a full announcement, but we’ve opened our beta so people who are fleeing the core Nix community have a place to go.
Btw, probably well-known by those closely involved in Nix et al, there's also #TVIX by The Virus Lounge, a #Rust reimplementation of the #Nix language. And a project that got funding from #NLnet@NGIZero