From 68b00cdf45551ba64c4f7217963055fc5a1a0cc4 Mon Sep 17 00:00:00 2001 From: Mason Reed 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/high_level_il/lift.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'rust/src/high_level_il/lift.rs') diff --git a/rust/src/high_level_il/lift.rs b/rust/src/high_level_il/lift.rs index fd0b9398..ab04f44b 100644 --- a/rust/src/high_level_il/lift.rs +++ b/rust/src/high_level_il/lift.rs @@ -1,5 +1,5 @@ use super::operation::*; -use super::{HighLevelILFunction, HighLevelInstructionIndex}; +use super::{HighLevelExpressionIndex, HighLevelILFunction, HighLevelInstructionIndex}; use std::fmt::{Debug, Formatter}; use crate::architecture::CoreIntrinsic; @@ -30,8 +30,8 @@ pub enum HighLevelILLiftedOperand { pub struct HighLevelILLiftedInstruction { pub function: Ref, pub address: u64, - // TODO: Please i need expression - pub expr_index: HighLevelInstructionIndex, + pub instr_index: HighLevelInstructionIndex, + pub expr_index: HighLevelExpressionIndex, pub size: usize, pub kind: HighLevelILLiftedInstructionKind, } -- cgit v1.3.1