today I've heard for the first time about the #RigelA open-source screen reader project for #Windows written in #RustLang. Unfortunately only Readme has an English version, all other documents and code comments are in chinese, but the project seems very promising. Use Google Translate or another translator if you, like me, don't speak Chinese. https://gitcode.net/mzdk100/rigela
I am starting a new project that is intended to be designed as a (#p2p) protocol eventually with implementations in multiple languages. I know #Python well, but I have been learning #Rust and think I'll need to write at least some of the perf-sensitive components in Rust. Do I prototype it in Python and then rewrite in Rust later, or try and power through and write it in Rust now? #RustLang
edit: added hashtags fwiw
Currently in the process of rewriting my #transpiler from #nom v4.2 to #chumsky v1.0.0-alpha.6 🤓
It is a lot of fun so far, but I have to say these type signatures are wild!😄
I'm still struggling with it far more than I'd like, but I guess it is just a matter of time until intuition kicks in and it will become more and more natural.
Exciting project ahead!🙂
I'm even able to parse string literals with escape sequences - something I haven't even achieved with nom!
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?
Let chains in nightly #rustlang are nothing short of godly. I'm working on my compiler's IR optimiser, and I'm astounded at how many long, deeply nested tracts of logic used to detect certain patterns in the IR shrivel down to just a few lines while being easier to understand.
I admit that I was sceptical when I first heard about the proposal, but the lang team have smashed it out of the park. I think this is an ergonomic improvement on-par with the ? error propagation operator.
One thing I will say: Rust on the web is overkill. I know, it's tempting to have something like leptos and have a single language on both frontend and backend.
What you should be doing is using the web platform. Most work should be done on the server anyways, your front end code should only be used for progressive enhancement. The user shouldn't have to run JavaScript in order to use your site. Plain and simple.
Somehow, whenever I write Rust, I feel like it's not really for me. I always spend so much time dealing with Rust logic, and so little time on actually writing the code I want.
I can understand how it suits a lot of people to have an extremely clear visualization of the path their code takes when it runs, but I prefer to write less code, even in that means sacrificing performance.
Hm...I'm getting the impression that #Rust is increasingly met with a refusal by some people (it's an almost hateful attitude sometimes).
I wonder why. Of course there are a lot of layers to it, but one is definitely that Rust has gotten a lot more exposure to people and so there are just a lot more potential matches that lead to Err(()) and that's Ok(()) (sorry, pun intended).
But I wonder, if there's more to it than what meets the eye (feeling excluded/alienated/left behind?).
"If you're unlucky and you just tried to pretend complexity could be avoided altogether, it has no place to go in this world. But it still doesn't stop existing."
Hrmm, #rustnationuk24 it's only 10:15 and one of the speakers already dunking on PHP 🙄 I thought the #rustlang community was supposed to be welcoming, but apparently not.
A bit annoyed by the documentation situation with #rustLang... As with most things in Rust land, it's great if you use cargo and it really sucks if you don't.
Unlike rustfmt, rustdoc actually has to be able to compile the code so it needs access to all your dependencies. You can't just invoke rustdoc on foo.rs and call it a day. It really needs to be invoked by the build system. Worse, it doesn't support all the same flags as rustc, some of which are used by meson.
Welcome to Monday's edition of Cracking the Cryptic#bevymergetrain. Today we have 13 community-reviewed #opensource#rustlang#gamedev PRs in our #bevy backlog for me to take a look at :) There's a couple of truly exciting ones today, so do follow along.
Ok, so I have a Vec<(String, f32)> and I need to, somehow, make it [[String]], but I want to do it lazily instead of converting the whole Vec... #rustlang