You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm taking a look at binhex4's API and I already see something that's less than optimal. The current API design requires size_of_raw_binhex_text + size_of_decoded_data RAM to operate.
Would you be willing to change the hexbin function to operate in a streaming manner? (i.e. Take anything that implements the Read trait as input and implement Read similar to something like BufReader or flate2::read::GzDecoder)
If not, I'd be willing to take a crack at it... just not right now because the project where I need a BinHex4 decoder is on hold while I work on more pressing ones.
The text was updated successfully, but these errors were encountered:
I'm taking a look at
binhex4
's API and I already see something that's less than optimal. The current API design requiressize_of_raw_binhex_text + size_of_decoded_data
RAM to operate.Would you be willing to change the
hexbin
function to operate in a streaming manner? (i.e. Take anything that implements theRead
trait as input and implementRead
similar to something likeBufReader
orflate2::read::GzDecoder
)If not, I'd be willing to take a crack at it... just not right now because the project where I need a BinHex4 decoder is on hold while I work on more pressing ones.
The text was updated successfully, but these errors were encountered: