-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dyn
could be explained better
#183
Comments
Sure, a small note along with a link to the book would be good. I'd be happy to review such a PR.
This is the intended target audience of the edition guide.
Seems like a better fit for the book. |
I was sent here from rust-lang/docs.rs#374 , I guess I should reopen that one to have dyn docs that are not just related to editions?
What book? I found this issue by googling for "dyn rust" and not finding proper docs for a rust newbie. |
The issue tracker for |
Holy cow this is a bit confusing. I'd suggest to rename docs.rs to cratedocs.rs, I don't know.
So I open the issue there yeah? Yet another bounce :) |
I'd still be open to improvements here as well. ^^ |
Closing per #232, this section has been removed. Sorry about getting bounced around, it can be confusing, and perhaps the edition guide didn't make its intended audience clear. Trait objects (and the |
There are two issues with this page: https://doc.rust-lang.org/edition-guide/rust-2018/trait-system/dyn-trait-for-trait-objects.html
It doesn't explain where does "dyn" come from, is it from the word "dynamic"? It should mention dynamic dispatching AFAIU.
It's targeted to people that are already familiar with Rust (that is, the people that were already using Rust before dyn keyword existed). If a new developer comes, it's better to just talk about the new way of doing things, not just mentioning that dyn is some new way to do some old stuff.
The text was updated successfully, but these errors were encountered: