XIO

xWire

Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.

The Rust Programming Language Forum - Latest posts

Latest posts

Plugin Systems in Rust: Experiences, Trade-offs, and What's Missing?

shard7: Would you consider adopting an IPC/RPC-based approach instead, where you do not have to deal with using the C ABI? I tend to dislike RPC approaches because they're brittle even on single-host setups. Particular pain points: If the RPC server dies, in general what clients do is not cleanly defined. It could hang, fail silently, or even crash. The need to orchestrate multiple processes is a PITA, because it's not as simple as just starting or killing everything. It is entirely possible…

Is a personal Rust learning diary appropriate on this forum?

ShangBrol: That moves the burden of translation from one writer to all readers, including the mods. I, as a reader can easily ignore such posts, but for mods it might be not so easy. I consider that a better tradeoff than someone with weak English being unable to get assistance with Rust at all. And note that I'm not saying that the writer shouldn't translate at all - but I'd prefer to have both clear native language and a bad English translation done by the writer (using their choice of tools…

Is a personal Rust learning diary appropriate on this forum?

That moves the burden of translation from one writer to all readers, including the mods. I, as a reader can easily ignore such posts, but for mods it might be not so easy. Edit: I also think a diary is a blog not a series of forum posts, hence doesn't belong here. In addition, in the form of a diary it might be not so interesting to justify posting, a summary of the experience over some time might be preferable.

What is the reason behind inability to use several trait bounds for a trait object?

Hmm, I agree that that’s good general advice for a blanket impl, but it seems very unlikely to ever be applicable to the particular combo of Read + Write, and in particular will never enable the creation of a trait object (because you can't coerce Box<SomethingNotSized> to Box<dyn Trait> regardless of what Trait is), so it is not useful for a trait that exists for the sake of trait objects. Do you think it should be included anyway?

What is the reason behind inability to use several trait bounds for a trait object?

Pull request rust-lang/rust Correct and expand E0225 error explanation. (#166021) main ← kpreid:e0225 kpreid opened 03:48AM - 16 Nov 26 UTC +47 -13 * “Multiple types” should be “multiple traits”. * Closures are not relevant. (Th…is phrasing probably came from seeing `Box<Fn()>` as being something different from a normal trait, but today, `dyn` makes them all recognizable as trait objects.) * Explain and demonstrate two possible solutions for a problem that seems to require multiple traits, in…

Rust Declarative Macros: Organization, Scoping, and Common Use-Cases

As always, thanks a ton! StefanSalewski: That is a grammar issue, "defined it textually" would be a valid option. Yes, I was missing the word "it" here, that was a mistake. StefanSalewski: Are you sure you intend to use the verb "to err" here? I sometimes use "err towards" as a shortened form of the idiom "err on the side of ___" (definition). However, that might be a confusing rephrasing of the idiom, and additionally it's clearer to say "usually prefer" as you suggest. So I will change it to…

Colorless: Write once controlflow for synchronous and asynchronous code

I've been working on Colorlessgithub.com/veecore/colorless-rs, an experimental rust toolkit to address the classic "function coloring" problem without code duplication or coroutine overhead. Quick Taste Here is a streaming key-value parser driven by callbacks (`ColoredFnMut`): #[colorless(C)] fn parse_records<'a, S, D>(mut source: S, mut sink: D) -> Result<usize, ()> where S: ColoredFnMut<(), C, Output = Option<&'a str>>, D: ColoredFnMut<(&'a str, &'a str), C, Output = Result<(), ()>>, { let…

New crate seeking feedback, review, potentially long-term maintainers!

Certainly, you did an excellent work. Your code is a good documented and well structured. At quick glance, you pass multiple separate config parameters in some calls. I would prefer to aggregate the parameters under some structure. Even, if the structure will be changed in future, the signature of the methods will remain the same.

Why is "Write" in the Vec documentation?

user16251: What is its significance? My guess is that one might not realize, unless it was brought to your attention, that a Vec can function as a write buffer, which is quite useful. For example, you can have functions that output to a type that implements Write, and these will work whether you're writing to a file/socket, a buffered file/socket, or just an (in-memory) Vec.

Is a personal Rust learning diary appropriate on this forum?

Thank you for sharing that. My counterpoint for you to consider would be the following: a forum (or blog or whatever) is, by its nature, intended for public consumption. (If you want to keep a diary just for the sake of keeping a diary, then you could do it the old school way of writing it down in a private notebook). Given the fact that this is an English language forum (I don't actually know what the forum rules are on different languages, but it is de facto English language), then who are…

Is a personal Rust learning diary appropriate on this forum?

There’s something that’s been bothering me, so I’d like to say it. I don’t think it’s right for a forum to discourage other languages simply because English is the main language used here. I believe a forum should be welcoming to people who speak different languages. Also, I use both Japanese and English in my posts. That said, I really appreciate what you said about there being people who might be interested in following my learning journey. Thank you for that.

Is a personal Rust learning diary appropriate on this forum?

Well the "wrong" thing here, that I wanted to raise with the mods, is that this isn't the sort of forum where people keep personal diaries. It's also an English language forum, so I have to agree with the commenter in the other thread that having a learning diary, in Japanese, pinned to the top of the forum simply isn't what this forum is designed for. None of this is to say you shouldn't keep a diary - do whatever you want to. It's very common for people to do what you're describing, but they…

Is a personal Rust learning diary appropriate on this forum?

I flagged your original post for review by the moderators because my understanding is that this forum is not the right place for what amounts to a personal blog. Consider that every day when you update it, it gets bumped to the top of the forum; it basically becomes a sticky. Consider also if more people started doing the same thing with their own threads - it doesn't scale well. I just felt that, technologically, this website is not the right medium for your diary.

Is a personal Rust learning diary appropriate on this forum?

Thank you so much for your thoughtful reply! I also really appreciate your offer to communicate in Japanese. I’m glad you don’t have a negative view of my learning diary. I’ll take your words, “Be bold,” to heart. For now, I’ve decided to pause my diary until I’ve had some time to sort out my feelings.