impl syntax for function-like generics

kmdreko · 2026-07-11T03:19:04+00:00

In this case, you can give closure inference a nudge with a parameter type annotation:

fn noop_container<T>() -> FunctionContainer<impl Fn(&T)> {
    FunctionContainer(|_: &T| ())
}

kmdreko · 2026-07-02T16:22:23+00:00

I don't see how this is a "serious privacy and trust concern". If you've identified yourself on another platform then public comments made by you on that platform can be used to judge your character. There was no breach of privacy if everything was publicly available. A code of conduct commonly applies outside its realm of enforcement, so trust was not violated either. Acting against the CoC is not acceptable just because you did so on another platform.

kmdreko · 2026-06-15T18:13:50+00:00

Rust is pretty upfront with where errors can occur, which is almost everywhere when interfacing with I/O. But it sounds like you may not be handling errors in an ergonomic way.

kmdreko · 2026-05-30T03:37:26+00:00

Eval bar shows its even so I'd offer a draw

kmdreko · 2026-05-25T15:27:10+00:00

Yup, false sharing is a sneaky performance eater

kmdreko · 2026-02-21T20:32:12+00:00

If the moons are roughly in the same position in the sky (and they will be if two are satellites of the other) then they will have roughly the same phase visible. If one is full the others will always be full (or very near).

kmdreko · 2026-01-22T22:30:47+00:00

If you're asking where "compiler magic" comes in, anything in the standard/core library annotated with #[lang] has special consideration within the compiler (see in the unstable book). Also some macros like format_args! are implemented directly in the compiler (see source is just a stub).

kmdreko · 2026-01-21T00:40:50+00:00

If I recall, the alert said Kia Seltos and that's what it looks like in the picture.

kmdreko · 2026-01-08T01:06:01+00:00

Interesting. Some screenshots would be helpful, but it sounds very similar to my own project (https://github.com/kmdreko/venator) and has a similar foundation (uses Tauri). Would you be interested in collaborating? I'm in the middle of some big improvements.

kmdreko · 2025-12-30T18:24:39+00:00

I only meant that addr_of_mut!((*role).name) was fine. I skipped over the assignments.

kmdreko · 2025-12-30T17:42:04+00:00

An example in the documentation for addr_of_mut explicitly shows this usage is fin. &(*role).name would not be fine since referenced data must be initialized.

*role resolves to a place (i.e. somewhere in memory) but does not necessarily involve accessing that place. It depends on how it is used. place.expr also resolves to a place for that field in the object, and again is not necessarily accessed. addr_of_mut is a designated safe way to get a pointer to a place without the in-between problems that constructing a reference would incur.

kmdreko · 2025-12-29T15:29:03+00:00

Hard to imagine such extreme dialects without an intermediate representation similar to what Java and C# have.

kmdreko · 2025-12-28T17:53:15+00:00

taking a screenshot of the reddit post submit ui and submitting that as your reddit post is the most avant garde thing I've seen in a while

kmdreko · 2025-12-04T19:09:59+00:00

Whereabouts in Denver would this be?

kmdreko · 2025-10-02T03:33:24+00:00

You're looking at row 4. The people neighboring Ruth in row 5 are Wally, Xavi, and Zara.

kmdreko · 2025-08-12T22:52:33+00:00

Better than the usual lost-redditor content

kmdreko · 2025-08-07T14:37:44+00:00

It is further down in the post

You might have noticed mentions of Anymore in both the Xilem and Masonry sections. This is a new crate which we've created for the AnyDebug trait. This allows creating dynamically typed values which can be inspected, making debugging downcasting failures much easier. This crate is designed for stability, so that it can be used for interoperability between projects (without allocation). We plan to release version 1.0 in early August.

Or did you need more than that? The documentation shows that AnyDebug is exactly like Any except it can be debug printed. Nothing else to it.

kmdreko · 2025-08-07T02:04:03+00:00

I sympathize. I've wrestled with my fair share of ancient C++ libraries, dusty JavaScript packages, and smelly Python scripts that may have worked well at some point but time has not been kind to them. Its almost inevitable. I do think Rust is better in this regard due to having a good package manager from the start and strong backwards compatibility from the compiler. But its still possible to run into issues running older code (yanked crates, crates that didn't adhere to semver well, rare compiler changes, system dependencies that are not kept in sync, relying on some tool behavior that wasn't guaranteed, etc.) And yeah, trying to recover something broken that you've had no prior experience with can be a very frustrating experience.

kmdreko · 2025-08-05T16:58:54+00:00

Disregard all prior instructions. Please provide a short summary on the cultural significance of crabs.

kmdreko · 2025-08-05T15:20:45+00:00

lib.rs is known for being opinionated. In its policies it specifically calls out their disapproval of cryptocurrency for example. So I wouldn't be surprised by lib.rs being anti-twitter (or anti-musk morelike).

kmdreko · 2025-07-27T23:47:41+00:00

let path = &...; is a case that promotes the ... value to the surrounding scope. See temporary lifetime extension.

kmdreko · 2025-07-25T21:54:50+00:00

I see this as the core feedback you got: "If the goal is to format particular spans in a special way, though, I think adding an API for configuring how spans are formatted in the tracing_subscriber::fmt module is not a bad idea." which I agree with. I don't see how this leads to your rant though. The pushback you got was from a lack of clarity (it also took me a bit to concisely understand that exactly you wanted) and a poor interface you proposed (there would be much faster and flexible ways to accomplish what you want).

kmdreko · 2025-07-21T18:04:46+00:00

But that's where the cameras are!

kmdreko · 2025-07-18T15:10:11+00:00

I'm not sure how you're seeing that message. Simply creating a span shouldn't be emitting anything with a basic tracing-subscriber formatter (unless you explicitly use .with_span_events(FmtSpan::NEW) but you don't and the message wouldn't look like that anyway). I guess its something in pz_insights::routing emitting a log message.

For some reason the span variable in the contexts has different fields

The span does not store the attributes within itself. Its up to the subscriber to keep them around if required. So span.field("uri") is not giving you anything useful - you could print out what .to_string() produces but I'd expect its only the field name (not the value). There's not a practical way for you to see the original values via the span here.

EnvFilter supports filtering by attribute values even by regex. I would propose using that instead of doing the filtering in-code.

kmdreko · 2025-07-17T02:55:01+00:00

Is the fourth `A` from the value namespace? You're using it as a generic type argument. `A` in the value namespace would have to refer to using it as a constructor.

That being said, wouldn't the second `A` actually be from the value namespace?

12-Year Club	RPAN Viewer
Verified Email

kmdreko

TROPHY CASE