[Pre-RFC] NonInternalMut auto trait (never mind)

[F001]

This post is removed by the author. The idea is incorrect. Thanks for your attention!

[sfackler]

Note that it is not a breaking change. Since the behavior of changing keys while it is in the map is always not allowed at the very beginning, this RFC only turns this requirement from the documentation into a hard constraint.

Making code that used to compile not compile is a breaking change.

[jethrogb]

It’s entirely possible to write a type that has interior mutability and upholds the invariants necessary for HashMap and BTreeMap to work.

[sfackler]

This also breaks all code that is parameterized over a type used as a key in a hashmap or hashset.

[F001]

Em, you are right. Thanks for all your reply. I would like to withdraw this post.

Thanks again!

[KillTheMule]

As an aside, please don’t do that! It’s pretty frustrating to come by and only see the remnants of a discussion. Nobodys judging you for starting a thread that did not turn into a revolution, so just leave it be, others might be interested nonetheless.

[Eh2406]

Also, if you withdraw it then no one with the same idaya in the future can google to find the past discussion.

[F001]

Sorry for the inconvenience. My basic idea of this post is to introduce a auto trait NonInteriorMut to indicate whether a type has interior mutability or not. And add this trait as a constraint to the key type of associative containers (HashMap BTreeMap etc), to prevent keys being modified when they are in the container.

[system]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.