Skip to content

reference: vtable entries are resolved at runtime #31677

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 25, 2016
Merged

reference: vtable entries are resolved at runtime #31677

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
347a257
reference: vtable entries are resolved at runtime
ivan Feb 15, 2016
58f0d72
reference: vtable entries: copy @nikomatsakis's wording
ivan Feb 18, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/doc/reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3565,7 +3565,7 @@ Each instance of a trait object includes:
implementation (i.e. a function pointer).

The purpose of trait objects is to permit "late binding" of methods. A call to
a method on a trait object is only resolved to a vtable entry at compile time.
a method on a trait object is only resolved to a vtable entry at runtime.
Copy link
Contributor

@nikomatsakis nikomatsakis Feb 16, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I would probably say something like "Calling a method on a trait object results in virtual dispatch at runtime: that is, a function pointer is loaded from the trait object vtable and invoked indirectly."

The actual implementation for each vtable entry can vary on an object-by-object
basis.

Expand Down