Dzmitry Malyshau

What if I want a very specific set of bindings? Only a subset of entry points and constants, only stuff the gfx backebd would need, for example? Does (or will)...

List of entry points we need today: - choose_first_config - query_string - get_configs/get_config_count - get_config_attrib - bind_api - create_context - create_pbuffer_surface - destroy_context - terminate - get_platform_display - get_display -...

Currently asserts on this line: ```rust "namespace" => assert_eq!(value, "GL"), ``` EGL spec uses a namespace per `enum`, so clearly the expectations are different here :/

That sounds interesting! Could be out of scope for this crate though.

Hi everybody! There is a lot of stuff mixed up here. @A-R-M @StarArawn > Compilation failed: \n\n:47:43: error: no matching conversion for functional-style cast from \'void\' to IIRC, SPIRV-Cross has...

Heads up - we appear to suffer from this issue heavily in gfx-backend-metal.

I tried this piece of code in metal-rs with no success: ```rust impl DeviceRef { pub fn name2(&self) -> &str { // new method struct Foo(*const [u8; 5]); unsafe impl...

@SSheldon we are definitely considering that. It will be unfortunate to throw this out once the real static linking of selectors work out... Speaking of which, could anyone (including @jrmuizel...

We attempted to use the code @mystor provided, gone through a few iterations with them, but ended up with a linker error. The plan was to go back and try...

I confirm - the simple example works with this addition :tada: @mystor 's code is still failing to link though. One suggestion they had is that the trouble comes from...