Luca Palmieri
@lpalmieri.com
Author of zero2prod.com, a book on backend development in Rust, and https://rust-exercises.com.
Building pavex.dev, a new Rust web framework.
Principal Engineer at Mainmatter. Opinions are my own. He/him.
@algo_luca on Twitter.
Building pavex.dev, a new Rust web framework.
Principal Engineer at Mainmatter. Opinions are my own. He/him.
@algo_luca on Twitter.
I'll be a busy bee!
I'll kick off on November 2nd with a Rust-Python interoperability workshop. On November 4th I'll be @fasterthanlime's sparing partner in his unfair Rust quiz and I'll close down the conference schedule with a talk on dependency injection.
Looking forward 🚀
I'll kick off on November 2nd with a Rust-Python interoperability workshop. On November 4th I'll be @fasterthanlime's sparing partner in his unfair Rust quiz and I'll close down the conference schedule with a talk on dependency injection.
Looking forward 🚀
October 21, 2025 at 11:17 AM
I'll be a busy bee!
I'll kick off on November 2nd with a Rust-Python interoperability workshop. On November 4th I'll be @fasterthanlime's sparing partner in his unfair Rust quiz and I'll close down the conference schedule with a talk on dependency injection.
Looking forward 🚀
I'll kick off on November 2nd with a Rust-Python interoperability workshop. On November 4th I'll be @fasterthanlime's sparing partner in his unfair Rust quiz and I'll close down the conference schedule with a talk on dependency injection.
Looking forward 🚀
Looking forward to both @rustconf.com and @oxidizeconf.bsky.social, where I'll get a chance to dive into the details of the thought process and technical strategy that made this possible.
August 11, 2025 at 1:50 PM
Looking forward to both @rustconf.com and @oxidizeconf.bsky.social, where I'll get a chance to dive into the details of the thought process and technical strategy that made this possible.
Especially for compiler lints, but it's a step in the right direction.
June 26, 2025 at 3:50 PM
Especially for compiler lints, but it's a step in the right direction.
Little typo: jobs AT mainmatter DOT com
June 26, 2025 at 1:08 PM
Little typo: jobs AT mainmatter DOT com
Then might be now apparently, if one is well-versed enough in clippy-config-fu.
bsky.app/profile/lpal...
bsky.app/profile/lpal...
An even better solution from @briansmith.bsky.social: you can set an MSRV *just for clippy* via clippy.toml.
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
June 26, 2025 at 6:47 AM
Then might be now apparently, if one is well-versed enough in clippy-config-fu.
bsky.app/profile/lpal...
bsky.app/profile/lpal...
It turns out clippy has this at home, just named differently from what we would expect!
bsky.app/profile/lpal...
bsky.app/profile/lpal...
An even better solution from @briansmith.bsky.social: you can set an MSRV *just for clippy* via clippy.toml.
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
June 26, 2025 at 6:47 AM
It turns out clippy has this at home, just named differently from what we would expect!
bsky.app/profile/lpal...
bsky.app/profile/lpal...
An even better solution from @briansmith.bsky.social: you can set an MSRV *just for clippy* via clippy.toml.
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
June 26, 2025 at 6:46 AM
An even better solution from @briansmith.bsky.social: you can set an MSRV *just for clippy* via clippy.toml.
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one.
Back to fearless toolchain updates!
Found it: doc.rust-lang.org/clippy/confi...
Let me test it!
Let me test it!
Configuration - Clippy Documentation
doc.rust-lang.org
June 26, 2025 at 6:41 AM
Found it: doc.rust-lang.org/clippy/confi...
Let me test it!
Let me test it!
This would be news to me! Any docs?
June 26, 2025 at 6:39 AM
This would be news to me! Any docs?
Not every lint is machine fixable, as you know.
Regardless, if I am going down that path, I may as well pin a stable version via the toolchain file.
Regardless, if I am going down that path, I may as well pin a stable version via the toolchain file.
June 25, 2025 at 4:07 PM
Not every lint is machine fixable, as you know.
Regardless, if I am going down that path, I may as well pin a stable version via the toolchain file.
Regardless, if I am going down that path, I may as well pin a stable version via the toolchain file.
I don't think the two things should be tied.
I may want to benefit from features in the new release without necessarily wanting to do the work to fix new clippy lints at the very same moment.
I may want to benefit from features in the new release without necessarily wanting to do the work to fix new clippy lints at the very same moment.
June 25, 2025 at 4:05 PM
I don't think the two things should be tied.
I may want to benefit from features in the new release without necessarily wanting to do the work to fix new clippy lints at the very same moment.
I may want to benefit from features in the new release without necessarily wanting to do the work to fix new clippy lints at the very same moment.
Influencing the resolver behaviour, off the top of my mind.
Triggering other lints (e.g. incompatible msrv) if I end up using items that were introduced in 1.88.0 while my MSRV is 1.87.0.
Triggering other lints (e.g. incompatible msrv) if I end up using items that were introduced in 1.88.0 while my MSRV is 1.87.0.
June 25, 2025 at 4:01 PM
Influencing the resolver behaviour, off the top of my mind.
Triggering other lints (e.g. incompatible msrv) if I end up using items that were introduced in 1.88.0 while my MSRV is 1.87.0.
Triggering other lints (e.g. incompatible msrv) if I end up using items that were introduced in 1.88.0 while my MSRV is 1.87.0.