m4b

I want to make a 0.1.0 release with various things ironed out, tested, etc., then I think we can start getting ready for 1.0 :)

@fitzgen Yes, possibly. What specifically did you have in mind? So first some clarification, when you say "object format", are you are referring to the web assembly linkable object format?...

So I am leaning towards not adding wasm binary backends to goblin (with reasoning similar to @le-jzr 's objcopy "test" :) ) ; though adding it in the future is...

Ya that doesn't surprise me, since I'm sure PE had more bugs. Was Mach fuzzed too? I'm surprised their wouldn't be more bugs there Might also be good to fuzz...

I'd like to see more fuzzing before 1.0 release; in particular the mach-o and PE backends have been somewhat neglected :)

Haven't thought deeply about this suggestion, but this might also potentially fix what seems to be rather serious issue that, e.g., I can add some annotations to a serde struct,...

Yes, you're correct of course, not sure why I suggested this, just serializing what is there makes sense :)

Yes, similar to the example above, I was dealing with some C structs which had some header information, etc., then a large byte array containing image bytes, then some more...

It was the other way around, basically: ```c struct Foo { struct Header header; uint8_t data [0x8000]; struct Footer footer; } ``` In rust land I then wanted to: ```rust...

So I had something like this in mind :smiling_imp: , but it still overflows the stack (it also allocates twice which sucks): ```rust impl for Box where T: TryFromCtx>::Error> {...