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

Tracking Issue for const_cell_refs #79703

Closed
3 tasks
oli-obk opened this issue Dec 4, 2020 · 2 comments
Closed
3 tasks

Tracking Issue for const_cell_refs #79703

oli-obk opened this issue Dec 4, 2020 · 2 comments
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC

Comments

@oli-obk
Copy link
Contributor

oli-obk commented Dec 4, 2020

This is a tracking issue for the feature gate #![feature(const_cell_refs)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved Questions

  • How do we get the static checks back that ensure const FOO: &Cell<i32> = &Cell::new(42); does not compile successfully?
    • With the feature gate only dynamic checks (post-monomorphization during CTFE) catch it.

Implementation history

@oli-obk oli-obk added C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) labels Dec 4, 2020
@RalfJung
Copy link
Member

@oli-obk there was an implementation PR for this, right? Could you add a link to the issue description?

Currently this issue says nothing about what the feature even does.

@oli-obk
Copy link
Contributor Author

oli-obk commented Mar 26, 2021

This is a leftover of my failed attempt for #80384

The feature gate does not actually exist

@oli-obk oli-obk closed this as completed Mar 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC
Projects
None yet
Development

No branches or pull requests

2 participants