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

Unsafe Fields #273

Open
1 of 7 tasks
nikomatsakis opened this issue Feb 18, 2025 · 2 comments
Open
1 of 7 tasks

Unsafe Fields #273

nikomatsakis opened this issue Feb 18, 2025 · 2 comments

Comments

@nikomatsakis
Copy link
Contributor

nikomatsakis commented Feb 18, 2025

Metadata
Point of contact @jswrenn
Team(s) compiler, lang
Goal document 2025h1/unsafe-fields

Summary

Design and implement a mechanism for denoting when fields carry library safety invariants.

Tasks and status

@nikomatsakis
Copy link
Contributor Author

This issue is intended for status updates only.

For general questions or comments, please contact the owner(s) directly.

@jswrenn
Copy link
Member

jswrenn commented Feb 26, 2025

Key developments: In a Feb 19 Lang Team Design Meeting, we reached consensus that the MVP for unsafe fields should be limited to additive invariants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Project goal
Development

No branches or pull requests

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy