Skip to content
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

Correct "backwarding" behavior for self-calls in extended objects #702

Closed
lkuper opened this issue Jul 15, 2011 · 0 comments
Closed

Correct "backwarding" behavior for self-calls in extended objects #702

lkuper opened this issue Jul 15, 2011 · 0 comments

Comments

@lkuper
Copy link
Contributor

lkuper commented Jul 15, 2011

See src/tests/run-pass/anon-obj-backwarding.rs for an example/description of this bug.

@ghost ghost assigned lkuper Jul 15, 2011
lkuper added a commit to lkuper/rust that referenced this issue Jul 28, 2011
lkuper added a commit that referenced this issue Jul 29, 2011
Oops.  If we already have a backwarding vtable, that means that we are
currently building a forwarding fn.  (Progress toward issue #702.)
lkuper added a commit that referenced this issue Jul 30, 2011
Still working on getting backwarding to play nicely with self and
overriding.  Currently can't fix issue #702 without breaking how self
and overriding interact.
lkuper added a commit that referenced this issue Aug 4, 2011
using them yet.  Also, refactor process_fwding_mthd into separate
functions to handle backwarding and forwarding, and refactor
create_vtbl to be more digestible.
@lkuper lkuper closed this as completed in a334ada Aug 9, 2011
@lkuper lkuper removed their assignment Jun 16, 2014
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
A few missing *BSD poll flags

Added a few missing BSD poll flags for completeness.
pdietl pushed a commit to pdietl/rust that referenced this issue Apr 23, 2020
Re-add rust-docs component for lintcheck
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant