While a specification was started, I don't think you should expect a complete specification of semantics. Syntax should be fine for code that is not subject to transformations.
However, due to AST transforms, any "groovy" file you may read may have both other syntax and other semantics defined in custom projects. As an example, in geb certain codeparts will wrap each line in an assert statement at runtime. On Monday, May 23, 2016, Edinson E. Padrón Urdaneta < [email protected]> wrote: > Greetings Apache Groovy Community, > > I was wondering if we have a manual that describes the syntax and > semantics of the language. Something like Python's [1]. > > Thank you all for your time in advance. > > [1] https://docs.python.org/3/reference/index.html >
