You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm starting this issue so that we can track what modifications that rust as a language would require in order to safely support generic field projects. Feel free to add/modify as needed.
Pointer provenance - Right now, we don't have a way of stating that a given pointer is a part of a larger object; the most we can do is warn the user that if that is untrue, then UB might happen. It would be nice if the language had some method of guaranteeing that a given pointer is actually a part of a given type.
The text was updated successfully, but these errors were encountered:
RustyYato
changed the title
Modiciations to rust
Modifications to Rust
Jan 4, 2021
A nice to have is Rust auto generating Field types with some syntax. This would likely be more efficient than using a proc-macro and easier to use
This might also help with the pointer provenance problem as the only fields whose provenance we need to worry about are those that are being projected, which may simplify compiler checks somewhat (no clue if this is true or not, it just seems like it might be possible).
I'm starting this issue so that we can track what modifications that rust as a language would require in order to safely support generic field projects. Feel free to add/modify as needed.
The text was updated successfully, but these errors were encountered: