Hey everyone ! Am I the only one to have collision naming issues when generating obj-c headers ? If ...

# ios

[Anthony Pages]

Hey everyone !
Am I the only one to have collision naming issues when generating obj-c headers ?
If I have two interfaces with a same property but of different type, the compiler will add an _ at the end of one of them in the header.

interface A {
    val foo: Int
}
interface B {
    val foo: Int?
}

I will have the following header:

__attribute__((swift_name("A")))
@protocol A
@required
@property (readonly) int32_t foo __attribute__((swift_name("foo"))); // <----- foo: OK
@end;

__attribute__((swift_name("B")))
@protocol B
@required
@property (readonly) KotlinInt * _Nullable foo_ __attribute__((swift_name("foo_"))); // <----- foo with an underscore: NOK
@end;

I didn't find any issue on https://youtrack.jetbrains.com/ So I ask to you here before opening one.

_P.S: if props have the same type, there is no collision and no `_`_ added.

[basher]

Same as this: https://youtrack.jetbrains.com/issue/KT-43087

[Anthony Pages]

Oh thx! I saw the linked issue you already report on github. Sad we didn't have the possibility to be able to block this mangling. something like the JsName annotation for Objc would have been great