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

Implement vtable and cross-crate support for autoderef. #13087

Merged
merged 2 commits into from
Mar 23, 2014

Conversation

eddyb
Copy link
Member

@eddyb eddyb commented Mar 22, 2014

Implements vtable support for generic Deref impls with trait bounds.
Also fixes cross-crate inlining when using autoderef.

@eddyb eddyb changed the title Implement vtable support for autoderef. Implement vtable and cross-crate support for autoderef. Mar 22, 2014
bors added a commit that referenced this pull request Mar 23, 2014
Implements vtable support for generic Deref impls with trait bounds.
Also fixes cross-crate inlining when using autoderef.
@bors bors closed this Mar 23, 2014
@bors bors merged commit 087ec2a into rust-lang:master Mar 23, 2014
@eddyb eddyb deleted the fix-autoderef branch March 23, 2014 01:37
JohnTitor pushed a commit to JohnTitor/rust that referenced this pull request Aug 30, 2022
Remove auto-config patching from the VSCode client

This was introduced 4 months ago when we drastically changed the config keys. I'd like to remove this given I always felt uneasy doing edits to a users config from within r-a, and by now most if not all users should've swapped to a new enough version of r-a that should've updated their configs.

The extension will continue to work fine even with the outdated keys afterwards since we still do patching server side as well, and that one we'll have to support for quite some more time (if not until a proper 1.0 release where I assume we can allow ourselves some more user facing breakage)

(There also might've been a small bug in here that prevented users with certain outdated keys to prevent them from enabling certain keys for some reason)
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

Successfully merging this pull request may close these issues.

3 participants