Pascal
@killercup.de
Interesting! I’ve been using color-eyre because I liked the panic hook and the fact it collects span traces as well. If I could have context in one place for tracing and errors and get it in the right stacktrace-y report that’d be amazing
November 23, 2025 at 11:32 AM
Interesting! I’ve been using color-eyre because I liked the panic hook and the fact it collects span traces as well. If I could have context in one place for tracing and errors and get it in the right stacktrace-y report that’d be amazing
I have seen `.rustup/toolchains/$version/lib/rustlib/etc` exists but I didn't dare touch anything yet. Maybe soon
November 20, 2025 at 1:59 PM
I have seen `.rustup/toolchains/$version/lib/rustlib/etc` exists but I didn't dare touch anything yet. Maybe soon
For now, I'm at
```rust
#[cfg(debug_assertions)]
pub mod smallvec {
pub use std::vec as smallvec;
pub use std::vec as smallvec_inline;
pub type SmallVec = Vec;
}
#[cfg(not(debug_assertions))]
pub use smallvec::smallvec;
```
```rust
#[cfg(debug_assertions)]
pub mod smallvec {
pub use std::vec as smallvec;
pub use std::vec as smallvec_inline;
pub type SmallVec
}
#[cfg(not(debug_assertions))]
pub use smallvec::smallvec;
```
November 20, 2025 at 1:59 PM
For now, I'm at
```rust
#[cfg(debug_assertions)]
pub mod smallvec {
pub use std::vec as smallvec;
pub use std::vec as smallvec_inline;
pub type SmallVec = Vec;
}
#[cfg(not(debug_assertions))]
pub use smallvec::smallvec;
```
```rust
#[cfg(debug_assertions)]
pub mod smallvec {
pub use std::vec as smallvec;
pub use std::vec as smallvec_inline;
pub type SmallVec
}
#[cfg(not(debug_assertions))]
pub use smallvec::smallvec;
```
ohhh just learned about `allow_attributes_without_reason`! thank you!
November 19, 2025 at 10:01 AM
ohhh just learned about `allow_attributes_without_reason`! thank you!
That’s the best alternative name I’ve seen suggested ever :O
I still remember that when i started using rust (in 2014) I thought “unwrap, cool, like a box” and then realized it was not related to Box but to monads and that it also panics and I was very confused
I still remember that when i started using rust (in 2014) I thought “unwrap, cool, like a box” and then realized it was not related to Box but to monads and that it also panics and I was very confused
November 19, 2025 at 7:53 AM
That’s the best alternative name I’ve seen suggested ever :O
I still remember that when i started using rust (in 2014) I thought “unwrap, cool, like a box” and then realized it was not related to Box but to monads and that it also panics and I was very confused
I still remember that when i started using rust (in 2014) I thought “unwrap, cool, like a box” and then realized it was not related to Box but to monads and that it also panics and I was very confused
At @eurorust.eu I saw this talk eurorust.eu/2025/talks/d... about using Petri nets for deadlock detection. I'd love for there to be a way for the compiler/tokio instrumentation to emit something like this and flag issues like this one
EuroRust 2025 – October 9 & 10, Paris & online
EuroRust is a 2 day conference for the European Rust community – October 9 & 10, 2025 – in Paris & online
eurorust.eu
November 11, 2025 at 8:21 AM
At @eurorust.eu I saw this talk eurorust.eu/2025/talks/d... about using Petri nets for deadlock detection. I'd love for there to be a way for the compiler/tokio instrumentation to emit something like this and flag issues like this one
Great episode, just finished listening! Luckily never ran into this, but glad to be aware! The HN discussion is at news.ycombinator.com/item?id=4577... ftr
Futurelock: A subtle risk in async Rust | Hacker News
news.ycombinator.com
November 11, 2025 at 8:21 AM
Great episode, just finished listening! Luckily never ran into this, but glad to be aware! The HN discussion is at news.ycombinator.com/item?id=4577... ftr
not deny but
```toml
# Pascal is bad with numbers
cast_lossless = { level = "warn" }
cast_possible_truncation = { level = "warn" }
cast_possible_wrap = { level = "warn" }
comparison_chain = { level = "warn" }
range_minus_one = { level = "warn" }
range_plus_one = { level = "warn" }
```
```toml
# Pascal is bad with numbers
cast_lossless = { level = "warn" }
cast_possible_truncation = { level = "warn" }
cast_possible_wrap = { level = "warn" }
comparison_chain = { level = "warn" }
range_minus_one = { level = "warn" }
range_plus_one = { level = "warn" }
```
November 9, 2025 at 11:08 AM
not deny but
```toml
# Pascal is bad with numbers
cast_lossless = { level = "warn" }
cast_possible_truncation = { level = "warn" }
cast_possible_wrap = { level = "warn" }
comparison_chain = { level = "warn" }
range_minus_one = { level = "warn" }
range_plus_one = { level = "warn" }
```
```toml
# Pascal is bad with numbers
cast_lossless = { level = "warn" }
cast_possible_truncation = { level = "warn" }
cast_possible_wrap = { level = "warn" }
comparison_chain = { level = "warn" }
range_minus_one = { level = "warn" }
range_plus_one = { level = "warn" }
```
Like this? docs.rs/static_asser...
assert_not_impl_any in static_assertions - Rust
Asserts that the type does not implement any of the given traits.
docs.rs
October 21, 2025 at 9:21 AM
Like this? docs.rs/static_asser...
Feels the least surprising. For cli flags I’m less sure since they often imply “optional”
September 10, 2025 at 3:51 PM
Feels the least surprising. For cli flags I’m less sure since they often imply “optional”
Maybe it’s just me but an empty vec is a weird special case that I hate to have to think about whenever I see Vec<T>. I’d error out unless the code has `#[facet(default)]` (or an equivalent explicit marker)
September 10, 2025 at 3:49 PM
Maybe it’s just me but an empty vec is a weird special case that I hate to have to think about whenever I see Vec<T>. I’d error out unless the code has `#[facet(default)]` (or an equivalent explicit marker)
Probably! But for sure at EuroRust!
September 6, 2025 at 11:12 AM
Probably! But for sure at EuroRust!
Reposted by Pascal
Wrote a blog post about this, I thought it was quite interesting https://deterministic.space/bufwriter-lz4.html
Rust BufWriter and LZ4 Compression
Recently, I’ve been working on a Rust project again.It deals with bioinformatics data, which can be quite large,so I got to play with profiling and optimizing the code.I’ve done some of this in past, but this time it was actually useful.In this post, I want to talk about a small optimizationin working with LZ4 compressionthat made a big difference in runtime performance.
deterministic.space
July 9, 2025 at 6:46 PM
Wrote a blog post about this, I thought it was quite interesting https://deterministic.space/bufwriter-lz4.html
Almost forgot I had a blog but after working on a cool rust project again I was inspired to share some findings :)
July 9, 2025 at 6:44 PM
Almost forgot I had a blog but after working on a cool rust project again I was inspired to share some findings :)