bits->octets order parameter
Ferada opened this issue · comments
I used the library before the order
parameter was removed from the bits->octets
function and just maintained a local small patch to add it back - I can see how it's complicating the interface, so I could probably just use ironclad:integer-to-octets
and supply the value myself. That said, the docstring still mentions the parameter.
Sorry about that. I was in the process of migrating the library away from the ironclad
dependency, to reduce overhead and improve performance, but my work schedule got in the way. I will correct the docstrings today and lay out a clearer update path here in the issues. Thanks for pointing this out!