Kitlith

I've been putting off writing an issue about this for a while >_> ReadOptions has been referred to as this library's bag of cheats. I have a couple of things...

Improve support for serializing data containing offsets (FilePtr, etc.)

3

Here's what roblabla had to say (on discord): > actually with seek+write, fileptr seems doable with some global context. Here's the idea: when you get a FilePtr, record the current...

derive macro silently fails when ran on a tuple struct

1

Apologies, this isn't exactly a minimal test, just how I discovered it. ```rust use binread::{BinRead, NullString}; use binwrite::BinWrite; // this *compiles* but does not behave as exepected. #[derive(BinRead, BinWrite, Clone,...

Support for custom permissions for custom sections.

25

I'm not sure how any of this translates over to the mach file format, so I haven't touched it yet. Fixes #104 , though I haven't tested it yet. A...

[Feature Request] Ability to specify load addresses (generate ProgramHeaders, Segments)

9

For my usecase, I'm wrapping a memory dump in an ELF and bundling it with available symbols so that I can easilly open it up in something like ghidra. Unfortunately,...

RWX sections (or: custom section permissions)

7

Hey, I'm looking to use this crate to generate a msp430 binary from the equivilant of a flash dump and a list of symbols, for use with ghidra. In my...

Here's a list of packages that are not maintained according to messages: - babel-preset-es (consider babel-preset-env) - redux-ava - postcss-cssnext -> postcss-preset-env - mockgoose -> mongodb-memory-server - not-so-shallow - circular-json...

[Question] Is it intentional that you can impl Try{From,Into}Ctx multiple times for a type using different ctx types?

3

```rust impl for SomeType { /* does one thing */ } impl for SomeType { /* does something completely different */ } ``` is a situation that is totally possible...

derive(Pread) in structs with elements that don't use scroll::Endian as ctx

4

Writing an implementation for `TryFromCtx

> From this limitation, conditions with nested OR cannot be expressed easily, such as: > > - 🚫 (F && (G || H) && (J || K)) As I understand...