This post is very welcome. It’s sure more relevant than many posts made in this instance.

Please continue to post whatever you like, as long as it’s on-topic.

The uppercase A in Axium.

Very quickly skimmed Cargo.toml and main.rs.

• What’s with the title-case name?
• The name proximity to axum is also not cool.
• You should mention that this is built on top of axum in the project description.
• How did you end up using both lazy_static and once_cell, when OnceLock has been stable since 1.70 and axum’s MSRV is 1.75?
• Why did you copy-paste min-sized-rust flags?
• You can actually print like this:

println!("{proto}://{ip}:{port}");

instead of

println!("{0}://{1}:{2}", proto, ip, port);

and the positional indices are redundant anyway.

• Since you’re depending on tracing, you should actually use tracing::error instead of eprintln!("❌ ...").

Okay. I will stop here.

Reads okay for the most part. But I like how we see the same point about AI as a feature in some more serious real-life projects. There, we frame it as “Rust makes it harder for a ‘contributor’ to sneak in LLM-generated crap”.

Cool and all. But missing some experiments:

• cranelift
• multi-threaded rustc
• undoing type erasure after the split
• lto = "off"
• strip = false (for good measure)
• [PRIORITY] a website that works with Tridactyl✋

You need to call ./y.sh prepare again

Aha! Good to know. And yes, improved documents would be of great help.

Thanks again for working on this.

But running

./y.sh prepare
./y.sh test --release

does work. That’s what gave me the impression that clean all doesn’t actually clean everything!

Yeah, apologies for not communicating the issue clearly.

cp config.example.toml config.toml
./y.sh prepare
./y.sh build --sysroot
./y.sh clean all
# above commands finish with success
# below, building succeeds, but it later fails with "error: failed to load source for dependency `rustc-std-workspace-alloc`
./y.sh test --release 

And then trying to use the “release” build fails:

% CHANNEL="release"  ./y.sh cargo build  --manifest-path tests/hello-world/Cargo.toml
[BUILD] build system
    Finished `release` profile [optimized] target(s) in 0.03s
Using `/tmp/rust/rustc_codegen_gcc/build/libgccjit/d6f5a708104a98199ac0f01a3b6b279a0f7c66d3` as path for libgccjit
   Compiling mylib v0.1.0 (/tmp/rust/rustc_codegen_gcc/tests/hello-world/mylib)
error[E0463]: can't find crate for `std`
  |
  = note: the `x86_64-unknown-linux-gnu` target may not be installed
  = help: consider downloading the target with `rustup target add x86_64-unknown-linux-gnu`
  = help: consider building the standard library from source with `cargo build -Zbuild-std`

For more information about this error, try `rustc --explain E0463`.
error: could not compile `mylib` (lib) due to 1 previous error

I will make sure to report issues directly in the future, although from account(s) not connected to this username.

Oh, and clean all doesn’t work reliably. Since trying to build in release mode after building in debug mode then cleaning is weirdly broken.

And It’s not clear from the README how to build in release mode without running test --release. And the fact that all combinations of --release-sysroot and --release --sysroot and --release --release-sysroot exist doesn’t help 😉

@antoyo@programming.dev

I gave this a try for the first time. Non-LTO build worked. But LTO build failed:

x86_64-pc-linux-gnu-gcc-15.0.0: fatal error: ‘-fuse-linker-plugin’, but liblto_plugin.so not found

I don’t have the time to build gcc and test. But presumably, liblto_plugin.so should be included with libgccjit.so?

Great to see this progressing still.
Great to see you posting here as well.
All the best.

Where does one even start ?

In any rust project, you start with API docs, and the examples folder if one exists. Just make sure the examples belong to the current version you will depend on, not the master/main branch. The link above is from v0.13.1 for example.

Generally yes, unless it’s the original source of a story.
e-celeb content and news aggregators are never the original source of a story.

That some can and already do that on the video sites they already browse.

People like shorts too, but that doesn’t mean Lemmy should be infested with such content.

We went from spam “news sites” to spam videos. Maybe an “original source” policy should be applied by moderators!

This applies to both hare and on !rust@programming.dev

Doubly linked list is one of std’s collections. And safety in Rust is built on top of unsafely, because there is no way around that.

Did you try to actually look up literally anything before asking?! Because simply checking out std::collections docs would have given you some answers.

^{Who memory-holed 2021 an why❔😉}

They talk too much. But almost none of them actually code or know how to at a good level.

We have someone just like that here.

Now that others got all the technicalities out of the way, maybe ChromeOS/ChromiumOS would be something along the lines of what you’re looking for? not that anyone should choose to daily-drive it.

most Rust developers

survey participants != all rust developers

In fact, there is no reason for experienced Rust developers to participate in such surveys at all. I don’t.

Hell, the way the survey results are covered (not just here) tells me that maybe we should push for it to never be done (officially) ever again.