Skip to content

Conversation

@amgdev9
Copy link

@amgdev9 amgdev9 commented Jan 21, 2026

Exposes Mach-O Section32 and Section64 reserved1 and reserved2 fields to the Section struct

Copy link
Owner

@m4b m4b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to understand why you want this, and probably remove the Clone annotations, I don't see why that's relevant for this

}

/// An export trie efficiently encodes all of the symbols exported by this binary for dynamic linking
#[derive(Clone)]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

making this Copy, Clone makes more sense to me; i'm curious why you needed to clone this though?

/// An interpreter for mach BIND opcodes.
/// Runs on prebound (non lazy) symbols (usually dylib extern consts and extern variables),
/// and lazy symbols (usually dylib functions)
#[derive(Clone)]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto why do you need this clone?

}

/// A cross-platform, zero-copy, endian-aware, 32/64 bit Mach-o binary parser
#[derive(Clone)]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this clone? We've avoided these for compile time reasons at this point, and it's never been required in the past, why do you need this? Also adding all these clone annotations has ostensibly nothing to do with your PR title btw

Comment on lines +65 to +68
/// reserved (for offset or index)
pub reserved1: u32,
/// reserved (for count or sizeof)
pub reserved2: u32,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why exactly do you want to see these fields btw? did some real world usecase require it, or? can you elaborate a bit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants