Skip to content

Design meeting: Solution for NoCell and no_std #324

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.

Sign up for GitHub

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

Jump to bottom
Open
traviscross opened this issue Apr 16, 2025 · 1 comment
Open

Design meeting: Solution for NoCell and no_std #324

traviscross opened this issue Apr 16, 2025 · 1 comment
Labels
meeting-proposal Proposal for a lang team design meeting T-lang

Comments

@traviscross
Copy link
Contributor

Summary

Let's discuss the solution for NoCell with no_std as discussed here:

cc @p-avital

About this issue

This issue corresponds to a lang-team design meeting proposal. It corresponds to a possible topic of discussion that may be scheduled for deeper discussion during one of our design meetings.
@traviscross traviscross added meeting-proposal Proposal for a lang team design meeting T-lang labels Apr 16, 2025
@traviscross traviscross mentioned this issue Apr 16, 2025
Open
@traviscross traviscross moved this from Needs triage to Scheduled in T-lang design meeting schedule Jun 4, 2025
@traviscross
Copy link
Contributor Author

We scheduled for 2025-07-23 to see about unblocking NoCell by coming up with a solution to the problem of how to express the propagation of auto traits for owned types with PhantomData<_> in no_std cases where Box<T> isn't available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meeting-proposal Proposal for a lang team design meeting T-lang
Projects
T-lang design meeting schedule
Status: Scheduled
Milestone
No milestone
Development

No branches or pull requests
1 participant
@traviscross