Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support of ReadOnlySequence and IBufferWriter
See original GitHub issueDescription
MagickImage recently began support initialization from ReadOnlySpan<byte>, which is great! But some times source memory can be fragmented and to prevent heap allocation it would be nice to have initialization from ReadOnlySequence<byte>. Also writing output is still restricted to Stream and coresponding to Span’s it would be good to have overload for IBufferWriter<byte>.
Proposal
Add constructor overload MagickImage(ReadOnlySequence<byte> data) and coresponding Read overload.
Add Write overload MagickImage.Write(IBufferWriter<byte> buffer).
System Configuration
- Magick.NET version: Magick.NET-Q16-x64 8.1.0
- Environment (Operating system, version and so on): Windows 10 x64
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I added a unit test for this to make sure this works but it I only tested this with
1byte sequences. This probably fails with sequences of a specific size will add a test for this and get this fixed.edit: I am working on a fix and I will publish a new release in a couple hours.
Just realized it might also be possible to use the
ReadOnlySequence<byte>, will need to run some experiments.