You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2019/11/24 02:46:01 UTC
[jira] [Closed] (GROOVY-8321) !instanceof treated incorrectly in
type checker
[ https://issues.apache.org/jira/browse/GROOVY-8321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King closed GROOVY-8321.
-----------------------------
> !instanceof treated incorrectly in type checker
> -----------------------------------------------
>
> Key: GROOVY-8321
> URL: https://issues.apache.org/jira/browse/GROOVY-8321
> Project: Groovy
> Issue Type: Bug
> Components: Static Type Checker
> Affects Versions: 2.6.0-alpha-1
> Reporter: Paul King
> Priority: Major
> Fix For: 3.0.0-rc-1
>
>
> Currently in:
> https://github.com/apache/groovy/blob/183b8fbf0248a2dceffbba684e50c3c2c060e46c/src/main/org/codehaus/groovy/transform/stc/StaticTypeCheckingVisitor.java#L703
> The `instanceof` and `!instanceof` operators are treated the same when in fact the exact opposite is required.
> Consider the following code where the `instanceof` has been _accidentally_ replaced with `!instanceof`.
> {code}
> [42, 'bar'].each { doit(it) }
> @groovy.transform.TypeChecked
> doit(arg) {
> if (arg !instanceof String) {
> println arg.toUpperCase() // MME: Integer.toUpperCase()
> } else {
> // println arg.toUpperCase() // [STC] [Static type checking] - Cannot find Object#toUpperCase()
> println 'is a number'
> }
> }
> {code}
> We'd now expect the `toUpperCase` call to fail compilation but it succeeds and then fails at runtime.
> Bonus points if the commented line in the else clause can be made to work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)