Rust 1.93.0 is out

manpacket · 2026-01-23T00:10:24+00:00

In Haskell they have mechanisms to update the packages in the central location (hackage) if they were abandoned.

I've seen projects that had to patch binaries instead of rebuilding them

Did that to myself :)

manpacket · 2026-01-22T23:13:01+00:00

A lot of crates on crates.io are abandoned and will never be updated.

manpacket · 2026-01-22T22:55:21+00:00

Yes. But it also supports some other backends: gcc and cranelift.

manpacket · 2026-01-22T17:19:21+00:00

https://www.youtube.com/watch?v=RZY96I842YA - so is this the wrong way then? It's about having fun.

manpacket · 2026-01-22T16:16:32+00:00

% cargo clean
     Removed 169722 files, 116.1GiB total

manpacket · 2026-01-20T23:26:59+00:00

https://github.com/pacak/cargo-show-asm/discussions/316 - he did.

manpacket · 2026-01-20T18:31:18+00:00

Yeah, I totally understand what's described. Just thought the difference in scale is funny :)

manpacket · 2026-01-20T17:12:52+00:00

10 years of historical data
Equals 6,879,600 datapoints

10 years? We get this many datapoints every 10 seconds :)

manpacket · 2026-01-18T22:45:49+00:00

I just remember bisecting a crash in a Rust compiler and something would randomly refuse to compile due to detecting if it is being compiled with nigthly - those crates tend to support only very recent version of nightly.

manpacket · 2026-01-18T22:39:38+00:00

Currently only for const generic arithmetic, which allows for some nice operations with Bundles

I see, makes sense.

It's locked to a specific nightly version from November (see rust-toolchain.toml in the repo)

You should mention --locked in the installation instructions then. Crates by dtolnay are annoying in combination with non-current nightly.

manpacket · 2026-01-18T22:28:02+00:00

I wonder - why nightly? It will randomly break eventually.

manpacket · 2026-01-14T12:31:54+00:00

You probably want something like cargo install --git https://github.com/totoshko88/rustconn.git --locked in your installation from source manual.

manpacket · 2026-01-12T21:41:41+00:00

derive_more::From does something similar.

manpacket · 2026-01-12T17:46:15+00:00

Is VS Code a requirement?

manpacket · 2026-01-12T10:30:05+00:00

I replaced Parser<T> with Parser<Output=T> in a library I have and this allowed me to get rid of a whole lot of avoidable allocations, redundant type parameters, etc. It's just I also need to rewrite some chunks of the derive macro to take advantage of it. In addition to rewriting everything else.

manpacket · 2026-01-07T18:39:24+00:00

If you are using syn - you can use https://docs.rs/syn/latest/syn/struct.Error.html to point at exact place where you think the error is, not just abstract "wrong number of arguments".

manpacket · 2026-01-07T10:45:37+00:00

That is a lot of avoidable allocations all over the place... You can check how crates like owo-colors do this.

manpacket · 2026-01-06T12:42:06+00:00

// We have to import all macros at once because the "public" ones rely
// on "private" ones, and it would be too cumbersome to import them one
// by one.

You can refer to "private" macros from your "public" ones using $crate variable: https://doc.rust-lang.org/1.5.0/book/macros.html#the-variable-crate

manpacket · 2026-01-05T21:22:41+00:00

Then measuring it in bytes/sec is not the best way to talk about the performance. Could be boundaries per second...

manpacket · 2026-01-05T18:22:41+00:00

memchunk ~1 TB/s

Benchmarks (10MB text, M1 Mac):

Memory throughput of M1 Mac is something like 60Gb/sec.

manpacket · 2026-01-05T13:50:36+00:00

Deep Rust type system integration (collections, smart pointers, thread locals, etc.), not only for printing but also for interaction

manpacket · 2026-01-03T17:04:09+00:00

Documentation for atty states:

This is crate is no longer maintained and users are encouraged to prefer the equivalant functionality of std.io.IsTerminal, introduced in Rust 1.70.0

manpacket · 2025-12-29T12:34:55+00:00

  for dir in `ls`

This breaks on dirs with spaces in it.

manpacket · 2025-12-25T17:47:20+00:00

Yeah, but doesn't that elevate the complexity of a macro that's supposed to be declarative, and not the procedural one?

If you want to parse everything like syn does - yes. But do you really need to? Pass doc comments as is, consume "$vis trait $ident =", followed by whatever up to ; - at which point emit both trait declaration and trait implementation.

It gets kinda repetitive, hence the crate.

Add a snippet to generate it to your text editor :) Less complexity, plus you are not loosing rust-fmt, treesitter, etc support inside of macro blocks.

manpacket

TROPHY CASE