Laurent Gomila

> Ok, but should we add it anyway for the other SFML bindings (which are based on CSFML) ? Nop.

Is `sf::VertexBuffer` part of the latest version, or does it have to be released yet (I really don't remember 😁)?

Then OK, it should be in CSFML and SFML.Net too.

I'd say `sfRenderTexture_drawVertexBufferRange`.

We can have a single loading function in CSFML and SFML.Net, because we can pass null for shaders we don't want to load. This is not possible in C++ with...

> Something like this: dd15e59 ? What I meant is that we *don't* need this overload in C and .Net 😉

Error handling will completely change in a future version of SFML, and as you pointed, there are multiple sf::err streams in CSFML, so there's no easy solution.

Indeed. This looks like a missing feature in CSFML.

Or an extra `srgb` argument to all the create functions. I should make a quick review of the sfTexture API to figure out what's best.

Clamping would not work, see this: https://github.com/erikd/libsndfile/issues/16#issuecomment-9827957