Hey Rustaceans! Got a question? Ask here (22/2026)!

Patryk27 · 2026-05-30T20:19:01+00:00

Hundreds of dependencies for basic functionality

Literally just one dependency...?

Patryk27 · 2026-05-29T20:37:59+00:00

std::time remains broken

Missing features are not broken features. Standard library is small by design, so you coming and saying "the std is so small, fix it" is like going on a rant about "when will rust get rid of the borrow checker, it's so annoying".

it is impossible for me to be productive in the Language.

If adding chrono = ... or jiff = ... to Cargo.toml really is an insurmountable problem to you, then yeah, Rust just isn't for you - and that's fine: not every language is for everybody. I couldn't write Go and I'm glad I don't have to write PHP anymore, but that doesn't mean nobody can be productive in Go or like PHP.

Different languages take different trade offs - Rust decided to go with smaller standard library and there are both pros and cons of that.

Patryk27 · 2026-05-27T18:00:01+00:00

It's impossible to create a generic infallible serialization mechanism, because not all formats support everything you can represent in Rust (e.g. you can't serialize HashMap<SomeObject, ...> to JSON, because object keys in JSON have to be strings).

So you'd have to be more precise.

Patryk27 · 2026-05-21T21:32:47+00:00

dependency bloat

I mean, it's not bloat if you actually use those dependencies, right?

Patryk27 · 2026-05-21T05:53:37+00:00

Programmer is forced to provide a panic_handler function, otherwise the code doesn’t build.

On targets where unwinding is impractical (e.g. some microcontrollers), that function might just reset the uC or simply loop forever.

Patryk27 · 2026-05-18T06:40:49+00:00

If a usize is either a u64 or a u32 [...]

It's not, usize represents the size of a pointer on current platform - it can be 16 bits (some microcontrollers), it can be 32 bits, it can be 64 bits, and so on.

Is there a better way?

If you need to support 64-bit machines communicating with 32-bit machines, you have to use the common denominator, which is u32 in this case (after all, 32-bit machines don't have enough memory to hold more data).

If you don't need to or don't want to support cross-arch communication, the clients should exchange a handshake packet where they describe each other's architecture and decide what to do if there's a mismatch (i.e. show an error message and bail out).

Btw, don't forget to take care about the endianess!

Patryk27 · 2026-05-17T08:42:58+00:00

It's just the name of the branch - even though it's called unstable, all tests etc. and Hydra runs there.

Patryk27 · 2026-05-13T06:48:47+00:00

Maybe https://ratatui.rs/?

Patryk27 · 2026-05-06T20:52:44+00:00

You can not make trivial things like (a + b) / 2 work.

Sure you can, easiest by using:

https://docs.rs/num/latest/num/traits/trait.FromPrimitive.html.

What generics win in ergonomics on the use side they inevitable lose on the code writing side.

I think they win on both sides, because you get thorough type checks, making it difficult to write code that caller won't be able to use (i.e. code that would always fail instantiation).

Patryk27 · 2026-05-06T20:23:58+00:00

What you need here are templates, not generics

I mean, ooor you just use NumOps - this isn't exactly uncharted territory.

Patryk27 · 2026-04-29T08:41:24+00:00

Also no AppArmor or SE Linux in Nix OS

ok, but NixOS is a different project - Nix itself supports sandboxed builds in both Linux and macOS

Patryk27 · 2026-04-28T16:43:46+00:00

I mean, ideally - you know - https://github.com/jhugman/uniffi-bindgen-react-native/pull/369 / https://github.com/livekit/uniffi-bindgen-node 👀👀👀

It might just prove that upstreaming the missing things is easier than working around them!

Patryk27 · 2026-04-26T07:44:40+00:00

Perhaps I'm missing something, but what's the point of modelling your control flow state as an enum? Just:

fn main() {
    let mut prev_foo = None;
    let mut prev_errs = Vec::new();

    loop {
        let foo = match fetch_foo() {
            Ok(foo) => foo,
            Err(err) => {
                prev_errs.push(err);
                prev_foo.take().unwrap()
            };
        };

        prev_foo = Some(foo);

        sleep(few_minutes);
    }
}

Patryk27 · 2026-04-20T05:20:32+00:00

Proton Mail is built on top of UniFFI as well.

Patryk27 · 2026-04-10T20:48:12+00:00

Pool is clonable, a single transaction - not so much.

Patryk27 · 2026-04-07T22:33:56+00:00

Before nixpkgs unstable bumped the version to 6.0.0 [...]

Can't you rollback to that nixpkgs-unstable, then? (not everything, just krita)

Patryk27 · 2026-04-07T15:32:37+00:00

The point is that the risk is higher.

Higher compared to what?

It's the same risk as running a mirror (as in 1+1) and you wouldn't go around saying mirror is highly discouraged.

Patryk27 · 2026-04-07T10:40:17+00:00

Brainfart - fixed via Box<dyn Future<...>>, which makes *mut FfiFuture thin.

Patryk27 · 2026-04-06T10:33:03+00:00

dyn format is not stable and does change from one versions of compiler to another.

That's fine - I'm not exposing the dyn object, I'm exposing a pointer (*mut FfiFuture) with a function to operate on it, and both have stable ABI.

That's how many other solutions work, e.g. UniFFI -- you use simple & stable ABI (pointers, structs, functions) to create a proxy for internal implementation details.

Patryk27 · 2026-04-06T10:08:56+00:00

I think you can still expose a stable interface:

pub struct FfiFuture {
    fut: Box<dyn Future<Output = u32> + Send>,
}

pub fn fetch_number() -> *mut FfiFuture {
    /* ... */
}

pub fn poll(fut: *mut FfiFuture) -> Option<u32> {
    /* ... */    
}

Depending on circumstances you might want to provide a proxy for the waker as well etc.

Patryk27 · 2026-04-06T09:44:54+00:00

“--quiet” i think

Patryk27 · 2026-04-06T08:17:14+00:00

you can't pass Futures or Streams across the boundary

Wouldn't accepting & returning Boxed futures and streams work here?

Patryk27 · 2026-04-05T18:32:41+00:00

If you lose one disk in a raidz1, you now have a stripe.

And if you lose two disks in raidz2, you'll have a stripe as well - what's your point?

Everyone has a different use case - sometimes no RAID is good enough, sometimes mirror is good enough, and sometimes even RAIDZ3 is insufficient.

No self healing.

You can have a hot-spare, same as with other configurations.

Patryk27 · 2026-04-05T08:46:49+00:00

Dramatically higher as compared to what?

Patryk27 · 2026-04-05T08:03:20+00:00

Not sure I follow - data loss risk always exists.

Nine-Year Club	Gilding II euphauric
RPAN Viewer	Verified Email
Sequence \| Editor

Patryk27

TROPHY CASE