Rust

5965 readers

18 users here now

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

Wormhole

[email protected]

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

[email protected]

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

submitted 1 year ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

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

[–] [email protected] 3 points 1 year ago (1 children)

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?

[–] [email protected] 0 points 1 year ago

I guess it's only accessible to the mem::size_of because it has an implicit Sized bound as well. So really the bound is impl Into + Sized and I don't think the code using the function is assuming anything else.

But I do agree it feels weird. I feel like the function should know its return type regardless of how it is used?