Pre-RFC: Rust Safety Standard

Your point about the implicit right to insert UB is critical. This focus on "cross-version stability" is exactly what seems necessary here.

As a developer deeply invested in code safety and soundness, I'm curious: How do we translate this future-proofing requirement into the actionable guidance of the Standard? Should the RFC explicitly state that any undefined behavior in the contract (even if unreachable in the current implementation) must be treated as a hard failure? I'd love to hear your thoughts on how to word this to ensure developers take the documentation as a strict constraint rather than a suggestion. Thank you~