There is an annotation called 'DoNotInline' and acts as a compiler hint. So
maybe you can fork GWT and apply that annotation to the method. But then
you could also just change the implementation of the method to fit your
needs.
Obfuscation itself can only be enabled/disabled globally. The only thing
that is possible is to use JsInterop which allows you to define
interfaces/classes that are either implemented in JS and you just want to
access that implementation or should be exported to JS (without obfuscation
then obviously) so that plain JS can call into GWT code. But not sure if
hasTypeMarker() can be marked as such.
-- J.
Developer2011 schrieb am Freitag, 5. November 2021 um 00:15:39 UTC+1:
>
> To solve an issue, it would greatly simplify things to prevent the GWT
> compiler from inlining and obfuscating the internal GWT function
> hasTypeMarker(). That way, we can replace it in our own code. (Yes, not
> guaranteed to work, we know.)
>
> Is there any fine-grained control like this? We don't want to have to
> disable obfuscation and inlining for everything.
>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/a99538e1-4f70-49e8-9118-faaf15a123e0n%40googlegroups.com.
