Has a discussion about un-deprecating `@nativeGett...

# javascript

[Edoardo Luppi]

Has a discussion about un-deprecating @nativeGetter, @nativeSetter, and @nativeInvoke ever been started?
I think they're still the way to go, as annotation-based behaviors is effectively what Kotlin uses, and the unsafe js() alternative should be reserved for more peculiar use cases (e.g. complex externals fun with body).

[turansky]

For now I like WASM behaviour more

[turansky]

It works without annotations

[turansky]

Unfortunately invoke operator isn't supported right now

[Edoardo Luppi]

Does WASM simply look at the operator keyword?

[turansky]

Yes

[turansky]

As result - [] in JS = [] in Kotlin

[Edoardo Luppi]

Interesting. I'm just trying to think if there could be limitations with that approach 🤔

[Edoardo Luppi]

For instance, when using @nativeInvoke you're free to name the function as you like.
Although apart from that, I can't come up with anything else.

[turansky]

I don't know good use cases for such behaviour :(