Actually there is an even simpler code that avoids having to copy the header to
./nimcache
([gist](https://gist.github.com/mratsim/ea8c3fe07aaeffd41a9bb7fbdf2a1d16)).
Note: VScode and github properly highlight the emit.
import nimcuda/[cuda_runtime_api, driver_types, nimcuda]
> 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
