From 55379bb7ea8ddad827bddc341c3df2038fe4a9fd Mon Sep 17 00:00:00 2001 From: Smittyvb Date: Wed, 30 Jun 2021 09:07:47 -0400 Subject: [PATCH] simplify explanation comment Co-authored-by: Ralf Jung --- compiler/rustc_middle/src/mir/interpret/allocation.rs | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/compiler/rustc_middle/src/mir/interpret/allocation.rs b/compiler/rustc_middle/src/mir/interpret/allocation.rs index 9bc41da1b467..ea2b104b27bd 100644 --- a/compiler/rustc_middle/src/mir/interpret/allocation.rs +++ b/compiler/rustc_middle/src/mir/interpret/allocation.rs @@ -130,15 +130,8 @@ impl Allocation { // This results in an error that can happen non-deterministically, since the memory // available to the compiler can change between runs. Normally queries are always // deterministic. However, we can be non-determinstic here because all uses of const - // evaluation do one of: - // - error on failure - // - used for static initalizer evalution - // - used for const value evaluation - // - const prop errors on this since otherwise it would generate different code based - // on available memory - // - panic on failure to allocate very small sizes - // - actually panicking won't happen since there wouldn't be enough memory to panic - // - used for caller location evaluation + // evaluation will make compilation fail (via hard error or ICE) upon + // encountering a `MemoryExhausted` error. InterpError::ResourceExhaustion(ResourceExhaustionInfo::MemoryExhausted) })?; bytes.resize(size.bytes_usize(), 0);