-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Forwarding functions (from object coercions) should tail-call target #80
Comments
Shifted to rustc |
No longer relevant. |
oli-obk
pushed a commit
to oli-obk/rust
that referenced
this issue
Jul 19, 2017
Read discriminant as a signed integer.
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
unbreak openbsd and bitrig due to linking to rt
dlrobertson
pushed a commit
to dlrobertson/rust
that referenced
this issue
Nov 29, 2018
Update attributes.md
eddyb
pushed a commit
to eddyb/rust
that referenced
this issue
Jun 30, 2020
Add flag --api-guidelines to silence non-technical breaking changes.
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 1, 2021
Add classification functions
jaisnan
added a commit
to jaisnan/rust-dev
that referenced
this issue
Sep 6, 2024
Prevent pr approval from getting skipped when there is a non-approval review submitted on the PR. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we do an 'as' operation to build a new obj with a different-shaped vtbl, we currently use a vtbl full of forwarding functions (to make the cast constant-time). The forwarding functions (if we continue to use them) should end in tali-calls, not normal calls. Same as with closure helpers.
The text was updated successfully, but these errors were encountered: