From 68b00cdf45551ba64c4f7217963055fc5a1a0cc4 Mon Sep 17 00:00:00 2001
From: Mason Reed <mason@vector35.com>
Date: Fri, 30 May 2025 16:39:32 -0400
Subject: [Rust] Express expression vs instruction index for MLIL and HLIL APIs

This was done to fix unintended behavior using an instruction or expression index in place of the other.

Fixes https://github.com/Vector35/binaryninja-api/issues/6897
---
 rust/src/medium_level_il/block.rs | 2 --
 1 file changed, 2 deletions(-)

(limited to 'rust/src/medium_level_il/block.rs')

diff --git a/rust/src/medium_level_il/block.rs b/rust/src/medium_level_il/block.rs
index 1fcd51ca..162b19b0 100644
--- a/rust/src/medium_level_il/block.rs
+++ b/rust/src/medium_level_il/block.rs
@@ -14,8 +14,6 @@ impl BlockContext for MediumLevelILBlock {
     type Iter = MediumLevelILBlockIter;
 
     fn start(&self, block: &BasicBlock<Self>) -> MediumLevelILInstruction {
-        // TODO: instruction_from_index says that it is not mapped and will do the call
-        // TODO: What if this IS already MAPPED!?!?!?
         self.function
             .instruction_from_index(block.start_index())
             .unwrap()
-- 
cgit v1.3.1