You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very usefull annotation would be a @CalledFromNative that would be used to mark class methods that are meant to be called from native code. This annotation would allow for suppressing of the "method is never used" inspection and would in general help in clarifying the code. This would especially be useful in Android (Studio) projects that mix java and native code.
The text was updated successfully, but these errors were encountered:
It would also be useful in other contexts such as transpiling to javascript via tools such as J2CL and GWT where java code often exists so it can be called from javascript but may not be invoked from java. Although we mostly just add it to the list of annotations that define entrypoints.
Would it make sense to make an Entrypoint annotation that can be used to annotate other annotations that are put on entrypoints? I'm thinking it would go on annotations like org.kohsuke.MetaInfServices and this CalledFromNative annotation. Or maybe it could be used directly on program elements?
From https://youtrack.jetbrains.com/issue/IDEA-163737:
A very usefull annotation would be a
@CalledFromNative
that would be used to mark class methods that are meant to be called from native code. This annotation would allow for suppressing of the "method is never used" inspection and would in general help in clarifying the code. This would especially be useful in Android (Studio) projects that mix java and native code.The text was updated successfully, but these errors were encountered: