Skip to content

Add coding guideline(s) for trait upcasting #26

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

Open
PLeVasseur opened this issue Apr 3, 2025 · 0 comments
Open

Add coding guideline(s) for trait upcasting #26

PLeVasseur opened this issue Apr 3, 2025 · 0 comments
Labels
coding-guideline An issue related to a suggestion for a coding guideline

Comments

@PLeVasseur
Copy link
Collaborator

A really cool new feature in 1.86.0!

However, note this portion:

Note that this means that raw pointers to trait objects carry a non-trivial invariant: "leaking" a raw pointer to a trait object with an invalid vtable into safe code may lead to undefined behavior.

So it seems like a good idea to capture some coding guidelines around this.

@PLeVasseur PLeVasseur added the coding-guideline An issue related to a suggestion for a coding guideline label Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coding-guideline An issue related to a suggestion for a coding guideline
Projects
None yet
Development

No branches or pull requests

1 participant