Search

Items tagged with: Rust


#rust



Sad to see the the @rust forum uses HCaptcha, thus preventing me as a blind user from signing up and posting my projects there. I'd like to escalate this to the right people, but it's hard to do so without an account on the forums. Anyone got any suggestions/know who I can reach about this? #Rust #Rustlang #Accessibility


RE: hachyderm.io/@conjured_ink/115…

I’m gonna boost this again cause we really haven’t gotten very many applications but we could really really use the engineering help, esp if you’re an experienced #Rust #RustLang engineer.

Open source drive bys are great but having a set of folks who are willing and able to commit to just 5 hours a week would make a world of difference for the project. Please take a look and lmk if you have any questions!


Finally, after some months of refining, the "Incremental System Rethought" RFC is out!

This RFC has been through 6 full drafts, 1 conference, 5 months of design and a closed project goal. Go roast it.

github.com/rust-lang/rfcs/pull…

#rust #foss #programming #opensource


The #chatmail #rust core is the base infrastructure library used by all apps and bots. It contains all networking, encryption, email processing and implements all the relevant IETF email standards. It's a single central development place with which the whole ecosystem of clients and bots can upgrade consistently.

We are constantly trying to remove code, and to cleanup things. That's a must to keep a 8-year long evolved code base agile and adaptable. Key insight: The best code is no code ;)


🦀 It's not ready for an official announcement yet, but we're working on a small DB-backed worker queue in Rust.

github.com/mre/workers

It's a recurring ask from clients, and I couldn't find anything "production ready" out there.

It's built on top of crates.io's queue. We moved to sqlx (from diesel) as well.

Can we get some eyeballs on it? Feel free to comment here and/or create an issue. A retoot and a ⭐ would also help, of course... 😉

#rustlang #rust #workqueue


Who would like Rust in CPython 3.15?

@emmatyping and Kirill Podoprigora "propose introducing the Rust programming language to CPython. Rust will initially only be allowed for writing optional extension modules, but eventually will become a required dependency of CPython and allowed to be used throughout the CPython code base."

discuss.python.org/t/pre-pep-r…

#Python #Python315 #CPython #Rust




Here's a proof-of-concept example of a Delta.Chat bot for .NET

It's pretty basic, especially since I can't get #open-rpc-generator to generate #csharp code, seems to be limited to #rust and #typescript

To use it, follow the `import` instructions and provide your own implementation of `IMessageProcessor`.

#deltachat

github.com/timothyparez/deltac…



@Federico Mena Quintero I've figured it out finally. The issue was not parsing ipv4 addresses but using matches.from_os() on the socket argument.
I have changed it to use std::path::PathBuf and it's working fine for me now.
Huge thanks for friendly hint and looking at my code.


@Federico Mena Quintero Oh, huge thanks for taking a look. Yes it's clap 3. It's not my decision, I'm attempting to contribute to an existing project so if I can make it work without major changes that might be helpfull. As I don't feel qualified for making decisions when it comes to this. I'm novice when it comes to #rust.
--socket argument is required, other two arguments are supposed to be used together and this condition is tested at runtime.
So if I specify all three command line arguments, I am always getting that error.
I have attempted using os::str and casting but the issue remains. I am simply compiling the app with cargo build --release.
Have you been just adding stuff I may have overlooked when trying to simplify for posting or did you actually changed something please?


I'd like to parse ipv4 addresses given as command line argument values.
I have got two arguments accepting ipv4 address.
If I specify single such option all is fine.
If I specify both, I 'm getting error like this:

thread 'main' (624061) panicked at /home/peto/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/clap-3.2.25/src/parser/matches/arg_matches.rs:1879:13:
Must use `Arg::allow_invalid_utf8` with `_os` lookups at `[hash: A8F400C40154F09]`

This is simplified version of my code showcasing the issue:
```
use std::net::{IpAddr, Ipv4Addr};
use clap::{App, AppSettings, Arg, value_parser};

#[tokio::main]
async fn main() -> Result<(), Error> {
let mut app = App::new("Server APP")
.about("My super cool app")
.setting(AppSettings::DeriveDisplayOrder)
.setting(AppSettings::SubcommandsNegateReqs)
.arg(
Arg::with_name("socket")
.required(true)
.takes_value(true)
.long("socket")
.help("Unix socket path"),
)
.arg(
Arg::with_name("relayaddress")
.required(false)
.takes_value(true)
.long("relay-address")
.value_parser(value_parser!(Ipv4Addr))
.help("External relay ipv4 address used together with --listen-address to run behind a nat"),
)
.arg(
Arg::with_name("listenaddress")
.required(false)
.takes_value(true)
.long("listen-address")
.value_parser(value_parser!(Ipv4Addr))
.help("Local listen ipv4 address used together with --relay-address to run behind a nat"),
);
let matches = app.clone().get_matches();
if matches.is_present("relayaddress") & matches.is_present("listenaddress") {
let external_ip = IpAddr::V4(matches.get_one::<Ipv4Addr>("relayaddress").expect("Invalid address"));
let local_ip = IpAddr::V4(
matches.get_one::<Ipv4Addr>("listenaddress").expect("Invalid address"));
println!("Listening on local IP: {local_ip}");
println!("Relaying through external IP: {external_ip}");
}}
```

#rust #rustlang #programming #fedihelp


#rust


#rust



I used to use #OCaml quite a bit, though that was a number of years ago, and I use #Rust a lot now.

One of my main gripes about OCaml is how it wasn't very practical in some ways. There was no way to open a file read/write (very common for, say, databases), and because it lacked things like Haskel's typeclasses or Rust's traits, you'd use different functions to seek on a file opened for input vs. one for output.

Looks like it's still the same.


Les quería presumir mi tapete de #Rust hecho con telar de pedal.
#rust



I am slowly oxidizing my unix CLI. A lot of people have made rust based versions of common unix utilities and some of them are REALLY good.

Like fd-find for doing essentially find . -name blah. And rg (ripgrep) which does grep -R but it's aware of git, files like pyc or .bak files, and it excludes them by default.

Now I have sd which is hopefully replacing the last thing I used perl for. I write perl -pi -e s/x/y/g a lot. Just doing a quick string replace inside a file. So sd can start doing that.

I'm also trying to get used to zellij instead of tmux and starship for modern prompt decorations like the kids do.

These kids, my friends, are welcome on my lawn.

#rust #cli #linux







🦀 Flattening #Rust's Learning Curve | corrode

「 Your learning pace doesn’t have much to do with whether you’re smart or not or if you have a lot of programming experience. Instead, what matters more is your attitude toward the language.

I have seen junior devs excel at Rust with no prior training and senior engineers struggle for weeks/months or even give up entirely. Leave your hubris at home 」

corrode.dev/blog/flattening-ru…

#rust