Nim case insensitivity -> identifier clash about nimterop HOT 6 CLOSED

This is finally fixed. With the latest commit, you get a decent error message.

Error: unhandled exception: /nimterop/nimterop/getters.nim(127, 5) `not hasKey(existing, nimName)`
Identifier 'SDL_GL_CONTEXT_RESET_NOTIFICATION' is a stylistic duplicate of identifier 'SDL_GLContextResetNotification', use 'cPlugin:onSymbol()' to rename [AssertionError]

User is expected to skip the problematic symbol or rename using plugin.

from nimterop.

Another example from GLES2: GL_BYTE and GLbyte origination from typedef khronos_int8_t GLbyte; and #define GL_BYTE 0x1400

from nimterop.

@Araq - do you have any suggestions on how to differentiate these two? Here's the current output from nimterop:

type SDL_GLContextResetNotification* = distinct int
converter enumToInt(en: SDL_GLContextResetNotification): int {.used.} = en.int

type SDL_GLattr* = distinct int
converter enumToInt(en: SDL_GLattr): int {.used.} = en.int

const
  headerb = "b.h"
  abc* = 0.SDL_GLContextResetNotification
  SDL_GL_CONTEXT_RESET_NOTIFICATION* = 0.SDL_GLattr

from nimterop.

the const is lowercase, the type Uppercase.

from nimterop.

concrete proposals discussed here: https://github.com/genotrance/nimterop/wiki/identifier-mapping-proposal along with the approach I recommend: see proposal 4

from nimterop.

The new plugin system will allow the user to rename these problematic symbols per their preference. There's no clear solutions from the Nim compiler itself but we can at least allow the user to handle this situation for now. Nimterop will aim to provide clear errors and guidance so that users can figure out such situations clearly.

from nimterop.