@eniko My workaround would be just putting #define blit my_blit at the top of the file so you can still use the naming you prefer without the link error.
@eniko@dalias maybe intellisense would work better with #define blit(dest, x, y, source, transparentIndex) my_blit(dest, x, y, source, transparentIndex)
TBH even with FORCE_INLINE the function looks like trouble
@0x00string@eniko is it? wouldn't the functions be confined to a namespace (or whatever python calls it) there, so the "conflict" would be with allegro.blit() or similar, so it wouldn't matter at all unless you do `from allegro import blit`, which could be resolved with `from allegro import blit as ablit` or similar
@eniko lol this annoys me too, which is why in my lang I can assign aliases to external imports. Well, for this reason and to avoidMixingCases in my_codebase