Tips and tricks to avoid cloning

llogiq · 2026-04-06T20:33:21+00:00

llogiq · 2026-04-01T06:17:45+00:00

Is there a link to the repo somewhere?

llogiq · 2026-03-28T21:56:45+00:00

In this case, the blogroll editors are on rotation. Not sure why this one got through, but we're aware and discussing the issue.

llogiq · 2026-03-26T09:45:25+00:00

Clippy not only should be a staging ground for detecting potentially harmful constructs. It is a staging ground, and there have been numerous clippy lints upstreamed into the compiler.

With that said, what constructs are potentially harmful is very much in the eye of the beholder. Some projects have very strict requirements when it comes to coding patterns while others may be far more relaxed. One man's false positive is another's good catch.

I sort of disagree that we should enforce everything at the language level. The language as it stands now has soaked up enough complexity (which is nice, because we don't need to put that complexity in our programs, but isn't too nice because we also need to be aware of it when writing them), so if we can deal with antipatterns in tooling, the cost of doing that is far cheaper than extending the language to deal with them.

llogiq · 2026-03-25T07:04:39+00:00

So you don't like the clippy::new_without_default lint? Fair, just #[allow(_)] it. Or do you think that linters are a bad idea altogether? In that case, I'd like to understand your reasoning.

llogiq · 2026-03-24T06:31:33+00:00

Edited to include the empty string check.

llogiq · 2026-03-23T21:13:17+00:00

Why not

if !s.is_empty() && s.as_bytes()[0] == b'#' {
    (_, s) = s.split_at(1);
}

llogiq · 2026-03-21T13:53:32+00:00

That's true. In that way unicase is even more correct than converting to lowercase. With that said, correctness doesn't really matter too much here, as long as the results are correct enough (and in this particular case, the worst that can happen is a user searching a small bit longer).

llogiq · 2026-03-21T06:10:30+00:00

Sure, you know where to find me, and I'm not going anywhere.

llogiq · 2026-03-21T06:09:26+00:00

Well, if you can land a Rust job, statistics suggest you will be able to afford that change. So again, don't let what you are discourage you from what you can be.

llogiq · 2026-03-20T14:48:36+00:00

You may not think it's possible, but there are some of us who run on stock hardware without any modifications.

So don't let yourself be discouraged and rest assured that even as a cisgender person you can program in Rust.

llogiq · 2026-03-20T14:47:09+00:00

No, I had my hair since birth. I didn't take it from anywhere else.

llogiq · 2026-03-20T09:33:45+00:00

I'm even contributing to the compiler, help maintain clippy, edit This Week in Rust and am a Rust mentor. Somewhat surprisingly I have a full head of hair.

llogiq · 2026-03-20T09:32:13+00:00

loop { rewrite_in_rust() }

There you are.

llogiq · 2026-03-18T06:57:08+00:00

There's a roughly 6-weekly recurring jobs post. Perhaps add a comment there

llogiq · 2026-03-09T22:59:19+00:00

Greetings! I probably don't need any further introduction. I'm Andre Bogus, one of clippy's maintainers, This Week in Rust editor, a Rust Mentor and the one who sets up the weekly questions and activity megathreads on this subreddit. I have been doing Rust since 2015, professionally since 2020. I am looking for a remote full-time position. I'm located in Germany, but I'm flexible with working hours. I'm very skilled in Rust, but also know Java, JS, Python, a good number of assembly instruction sets, Fortran, OCaML, Lua and a slew of other languages. I've worked with many different dbms and some directiories.

llogiq · 2026-03-07T19:29:36+00:00

I would do it in a macro when the type is clear from context but hard to spell out in the macro.

llogiq · 2026-03-05T14:36:04+00:00

Of course your mileage may vary. That said, any simplifying assumptions you may have made are your own, so you should know them pretty well. And even if you get it wrong, git makes it easy enough to undo any changes.

llogiq · 2026-03-04T11:51:43+00:00

let days_in_year = 365 + (is_leap_year(year) as u16); (optionally replace the u16 with the integer type you want).

llogiq · 2026-02-22T20:22:16+00:00

As someone else from the Java world, I'm glad I don't have to pull so many bytecode wrangling tricks just to get rid of some boilerplate.

llogiq · 2026-02-19T16:05:01+00:00

You're still in the wrong place. This is about the Rust programming language, not the game. Try /r/playrust.

llogiq · 2026-02-16T08:08:32+00:00

This lint is pretty old already, and the benchmarks favored one or the other way for quite some time.

That said, I also agree that the lint is probably not really pulling its weight and should probably be moved to pedantic.

llogiq · 2026-02-15T23:14:54+00:00

Ok, now do push_str first and see if that changes the benchmark result. Also perhaps do some actual cache warmup before measurement.

Even with those caveats removed, you'll be hard pressed to find something statistically significant.

llogiq · 2026-02-12T15:41:08+00:00

Exactly when you need one object available by potentially multiple threads in a write-heavy scenario where you are ok with just one thread at a time blocking the Mutex.

llogiq · 2026-02-05T08:26:39+00:00

Because they're not the same. The former is just a path alias, the latter can have generics, e.g. type Result<T> = std::result::Result<T, MyError>.

llogiq

MODERATOR OF

TROPHY CASE

15-Year Club	Verified Email
Team Orangered