this post was submitted on 18 Jul 2023

22 points (100.0% liked)

Rust

5981 readers

29 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

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev

22

Rustc Trait System Refactor (blog.rust-lang.org)

submitted 1 year ago by Arbitrary@lemmy.fmhy.ml to c/rust@programming.dev

1 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Bogasse@lemmy.world 3 points 1 year ago

I'm surprised by the ambiguity shown in the last example. Shouldn't the concrete return type for an impl Into<u32> be completely inaccessible outside of the function? Otherwise it would allow to introduce breaking changes without changing a function API.

But in this case, how would it be possible that impl_trait().into() is an u16?