I'm trying to use svdtools::patch::process_file within a build.rs and running into some friction. My crate generates the input svd file under cargo's ${OUT_DIR}, which requires modification of the _svd value in the patch file. In order to not modify the revision controlled patch files I now need to copy them to a temporary working location. For this use case coupling the svd path into the patch file introduces a lot of unnecessary complexity.

Proposal:
I'd like an ex: svdtools::patch::process_reader that instead of searching for the "_svd" value would take the svd content as a std::io::Read and return a std::io::Read of the modified svd. That would allow the caller more flexibility to handle the svd content independent of the patch content. I think the rest of the patching logic could be shared with process_file.