groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <>
Subject [jira] [Commented] (GROOVY-8570) Support Warnings in Groovy Compiler
Date Thu, 17 May 2018 23:20:00 GMT


Paul King commented on GROOVY-8570:

That issue is only 3 days old but the topic has been discussed before:


I just created the issue so we don't forgot to address.

> Support Warnings in Groovy Compiler
> -----------------------------------
>                 Key: GROOVY-8570
>                 URL:
>             Project: Groovy
>          Issue Type: New Feature
>          Components: Compiler
>    Affects Versions: 3.0.0-alpha-3
>            Reporter: mgroovy
>            Priority: Major
> * To warn Java developers using e.g. non-idiomatic Groovy constructs which only exist
to support copy-and-paste Java-to-Groovy code compatibility, The Groovy compiler should support
compiler warnings in addition to compiler errors.
>  * Warnings should by default only be emitted in special circumstances such as the one
described above, and not spam developers with an endless stream of, often subjectve, messages
on "how to use Groovy correctly".
>  * Sample warnings:
> # WARNING: Using curly braces Java style array literals (\{...}) is not idiomatic Groovy.
To avoid confusion with Groovy closures, it is recommended to use the performance-identical
Groovy square bracket list literal syntax ([...]) instead.
> # WARNING: The 'var' keyword is currently only an alias to 'def' (i.e. Object) in Groovy.
To get reassignment type safety use an explicit type instead.

This message was sent by Atlassian JIRA

View raw message