I think these 2 functions are used by
queue as callbacks for sorting. I have no problem with any other functions inside GLFW. AFAIK, these 2 functions are NOT externally visible. Have a look where they are used!
I compile GLFW to be statically linked, so when I change the default calling convention, for all the GLFW's
externally visible functions I have no problem. But these functions are only used used internally (I believe). And the problem is
queue expects them as __cdecl, it has nothing/little to do with the default GLFW calling convention, this has to do with GLFW usage/compatibiliy with the
If I create a Windows callback function, eg. WndProc. I need to make sure the calling convention for this specific function never changes (even if I change the default calling convention of my app) because windows expects the callback to be using a (hard-coded / specific) calling convention, the only way to do this is by hard coding the callbacks calling convention, so when I change my applications default calling convention to __stdcall, __fastcall, __vectorcall etc. The WndProc stays compatible with the expected calling convention of windows. The same thing applies to these functions.
Anyways, it was just an observation, I'll just keep making these 2 changes. I don't know what a Github issue or pull request is. I just use your forum. No worries!