I do think that "Face Screaming in Fear" is indeed the only appropriate reaction to a compiler parsing escape sequences outside of character/string literals.

Also, it seems strange to add a detector for this specific case instead of actually fixing the IDE's parser to match the language's correct syntax rules.

Why would they use "Easter Egg" to describe "lightly obfuscated code"? They are two different things. Easter Eggs have no special need for obfuscation in source code, just in UI.

Especially for Java, not JavaScript where source code is at least slightly relevant to the end user experience?

It reminded me of isUserAGoat https://developer.android.com/reference/android/os/UserManag...()

This reminds me a bit of the "Trojan Source" paper.

https://trojansource.codes/

undefined

Is this inspection an easter egg itself?

undefined

undefined