Dmitri Shuralyov

Didn't we already do that via https://github.com/go-gl/gl/issues/46, https://github.com/go-gl/glow/pull/71 and https://github.com/go-gl/gl/pull/49?

> the feature request is to unconditionally append \x00 to the C strings produced by gl.Strs ~~IIRC, I think it was a design decision not to modify input strings in...

Sorry for trigger happy comments, I'm coming back to this after a long time. To summarize my stance on this, I'm open to discussion if additional information and motivation is...

@docuys I suggest looking at the examples in https://github.com/go-gl/example. `gl41core-cube` in particular uses both `gl.CreateShader` and `gl.Strs`, see [here](https://github.com/go-gl/example/blob/ee0644b7c5650555db3c0f4d04f9ef5716e6c6ac/gl41core-cube/cube.go#L178-L183).

> how feasible is this? I don't know of a way of doing this. If someone knows a way, please share.

Indeed. However, there's only 8 of them (compared to hundreds or thousands of Go types), and I don't think they should've been exposed in the first place. I don't know...

I think we did reach agreement. We talked on slack and I left some comments on the proposal document. As long as you're willing to help maintain the Windows cgo-free...

I have never used any of the `*Debug*` functions in `gl`, so I can't say.

I'll comment on a small part of this issue (all I can do at this time): > As for 2, I'm kind of partial to keeping the current projection/transformation features...

Breaking change is okay if it's neccessary/unavoidable, as the current code is unusable. But it's a matter of figuring out whether that's the best fix. But this issue, isn't it...