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

declare_interior_mutable_const (and borrow_interior_mutable_const?) should probably use Freeze #14222

Closed
GrigorenkoPV opened this issue Feb 15, 2025 · 2 comments
Assignees

Comments

@GrigorenkoPV
Copy link
Contributor

GrigorenkoPV commented Feb 15, 2025

instead of hardcoding a list of known-to-be-interior-mutable types and then doing a recursive search for them inside of a struct.

Mentioned in #14125 (comment)

@cyrgani
Copy link
Contributor

cyrgani commented Feb 17, 2025

@rustbot claim

@Jarcho
Copy link
Contributor

Jarcho commented Feb 17, 2025

The listed types are non-Freeze types that should be treated as though they are for linting. e.g. Bytes uses an atomic internally, but the surface API doesn't expose the interior mutability.

@Jarcho Jarcho closed this as completed Feb 17, 2025
@Jarcho Jarcho closed this as not planned Won't fix, can't repro, duplicate, stale Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants