Yes, use `seq[byte]` already.
Sorry to be a bit of a pest, but I want to know if this is the thing I should
be doing or not for my Nim code now?
Okay, that sounds better to me. So for in my case with my stb_image wrapper,
should I switch the API now to use seq[byte] or should I hold off on it for a
little longer?
> In the issue ticket I linked, Eduardo Bart mentioned that int the Nim
> codebase that string is also used as a buffer (instead of a seq[uint8]), e.g.
> readFile() and writeFile(). Where even the data those procs could be
> returning binary and not text.
That is correct. But in the longer
This stems from some discussion I've had on the stb_image bindings:
[https://gitlab.com/define-private-public/stb_image-Nim/issues/4#note_40535183](https://gitlab.com/define-private-public/stb_image-Nim/issues/4#note_40535183)
I'd like some discussion on the use of the string datatype for