this post was submitted on 01 Sep 2023
17 points (87.0% liked)

Rust

6005 readers
3 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] 0xDEADBEEFCAFE@programming.dev 3 points 1 year ago (1 children)

Number 4 is only about not returning impl Into and instead just returning T.

[–] KillTheMule@programming.dev 0 points 1 year ago (1 children)

Hmm, right. I think it still might be warranted in niche cases, but trying to think of such a case made it pretty protracted in my head... maybe when functions can also be called for side effects, and the into conversion is costly and the caller might not care about the return value?

[–] anton@lemmy.blahaj.zone 1 points 10 months ago

Such a case would be the single function having a side effect*. This allows the caller to chose when to execute the side effect or to drop the result without executing it.

In my opinion that is fine with fn_once but not into because of the implicit contract of these traits.

* = I'm counting expensive computation, but not allocation and memcopy as a side effect in this comment.