# TWiR quote of the week

**URL:** <https://users.rust-lang.org/t/twir-quote-of-the-week/328>\
**Category:** community\
**Created:** [February 13, 2015, 6:51pm UTC](https://users.rust-lang.org/t/twir-quote-of-the-week/328 "2015-02-13T18:51:54Z")\
**Posts on this page:** 1\
**Showing post:** 1792

<div class="post-metadata">

**Author:** ![kleinesfilmroellchen](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/kleinesfilmroellchen/32/48336_2.png) [@kleinesfilmroellchen](https://users.rust-lang.org/u/kleinesfilmroellchen)\
**Post date:** [August 27, 2026, 7:35pm UTC](https://users.rust-lang.org/t/twir-quote-of-the-week/328/1792 "2026-08-27T19:35:42Z")

</div>

> <https://github.com/rust-lang/rfcs/pull/4001#discussion_r3825423816>
>
> "program leaks secrets" is not something that you can define as a property of an… AM execution, so I don't think we can have Miri detect this or call it EB. (Formally it's a hyperproperty, you need to define a notion of "public"/"secret" data and then compare \*two\* runs of the program to determine that a secret was leaked.)
> 
> \> A simple operational semantics would be a naive "taint tracking" model where bytes that were uninit and got frozen are still recorded as being "tainted" by uninit-ness,
> 
> I think you are inventing provenance for integers. Please, let's not.

> I think you are inventing provenance for integers. Please, let's not.

Insightful opsem commentary by @RalfJung while discussing the `MaybeUninit::freeze()` RFC.

---

_[View the full topic](https://users.rust-lang.org/t/twir-quote-of-the-week/328)._
