Jamey Sharp

I really like your external-file proposal, to avoid having to modify the vendor-provided files. It doesn't have to completely ignore the original SVD, though. For one thing, it could check...

@idubrov, good point about duck typing. I can't imagine a circumstance where two peripherals with identical registers would need different types. So maybe the external file mapping definitions back to...

While I agree that both `.reset` and `.write` need to _behave_ differently on peripherals with different reset values, that has no effect on their API—they are source-code compatible. So I'd...

That's a reasonable position. I'm not sure I agree, but I'd be happy to see a version of svd2rust that addresses my other concerns without being generic over reset values....

I've just written a quick hack at using svd-parser to identify duplicate peripherals across one or more SVD files (https://github.com/jameysharp/share-svd). Most of the code involves re-implementing only the parts of...

Thanks @japaric, the cluster reporting is definitely an improvement... although it didn't compile as-is for me, because the map's keys don't implement `Debug`. So I've pushed to my repo a...

I think you can make this available without breaking the existing libfuzzer crate API by splitting the crate into two parts. One crate links in the ["no-main" version](https://www.llvm.org/docs/LibFuzzer.html#using-libfuzzer-as-a-library) of libFuzzer...

I'm interested in this because when I run a fuzz target against an existing corpus, I'd like to gather statistics from inside the fuzz target and report them when the...

I came here to suggest this too. For example, I'd like to allow scripts from twitter.com but only when I'm in the permanent container I use for accessing Twitter. Although...

I was thinking about opening a separate issue for that. Seems to me that `Request` and `Response` should have `parts` and `parts_mut` methods to match the existing `body` and `body_mut`...