`mimalloc` is not being linked when building with the Cargo with LTO enabled. about hunt-rs HOT 4 CLOSED

The deployment worked as expected, closing the issue.
If more problems arise please reopen it.

from hunt-rs.

Thank you for opening the issue!

I didn't know hunt was in the AUR, that's great!

Regarding the problem, LTO provides a small but measurable boost in performance, and mimalloc a pretty massive one (~15% from my benchmarks), so it would be great if both could be kept.

Does the workaround have any downsides?
If not, I'll add it to the main repository to avoid errors on other packaging systems.

from hunt-rs.

Does the workaround have any downsides?

Nothing I can think of, I guess maybe build.rs is being compiled under-the-hood and that means slower build times, but I doubt that it would be significant difference to notice by most people, after all what this "program" does is to print a single message to stdout for Cargo to parse.

I should also say I've only reproduced this bug on Linux and I don't know how build.rs or this bug affects other OSes, I've also haven't dig enough yet with your dependencies or even features to know whenever you use mimalloc library outside of Linux and if it is used as a feature that can be disabled with the Cargo or not. You might consider writing a bit more dynamic build.rs if the use of mimalloc is different.

I didn't know hunt was in the AUR, that's great!

I've started maintaining it quite recently, mostly because I felt to be able to adopt some orphaned package and I went for the most popular yet flagged as outdated one back then. I also have some experience with Rust (which will definitely come in handy), it's nothing impresive (I see myself still as a beginner, as I still have to become way more familiar with a language syntax like standard library, macros, multi-threading, practical use of async and C interoperability to consider myself knowledgeable enough to see myself as a Rust intermediate dev).

If you want to, you might share there your AUR username and I might transfer package ownership to you or make you a co-maintainer, so you might as well by yourself maintain hunt. For me, stuff like version bumps etc. are quite relatively easy to do, I've already made a quite clever script to automate it and a GIT repo containing a submodules to maintain it all in more centralised way. I'll try to share that configuration soon with a bug tracker over a GitHub.

from hunt-rs.

I'll add the build.rs file then, if the deploy workflow fails then we'll look for other solutions.

AUR

Oh, I don't use Arch anymore, I was just suprised that hunt was being mantained in the AUR.
If you could continue mantaining it, I'd appreciate it.

from hunt-rs.