4 ms·
I am not sure what is the point of this? (of course except for "because you can", which is a good reason to do things, sure) Why be cgo-less, when in the end,
by shp0ngle 4y ago
I am not sure what is the point of this? (of course except for "because you can", which is a good reason to do things, sure)
Why be cgo-less, when in the end, it is just transpiled, with unsafe.pointer everywhere?
Do you gain some portability, that was not in the original C? Is there a speed gain, or ease to build gain?
Maybe the end "consumers" have it simpler, because they don't need to worry about cgo, but then it's harder to compile in the first place.