You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by pa...@apache.org on 2017/03/14 12:54:52 UTC
[2/3] groovy git commit: GROOVY-8119: Groovy Language Specification
documentation has bad internal links to "type checking section"
GROOVY-8119: Groovy Language Specification documentation has bad internal links to "type checking section"
Project: http://git-wip-us.apache.org/repos/asf/groovy/repo
Commit: http://git-wip-us.apache.org/repos/asf/groovy/commit/6aedd579
Tree: http://git-wip-us.apache.org/repos/asf/groovy/tree/6aedd579
Diff: http://git-wip-us.apache.org/repos/asf/groovy/diff/6aedd579
Branch: refs/heads/GROOVY_2_4_X
Commit: 6aedd5798b27bc8020b0d77abfd5c92e17388cc5
Parents: 9a7a9e4
Author: paulk <pa...@asert.com.au>
Authored: Tue Mar 14 21:05:52 2017 +1000
Committer: paulk <pa...@asert.com.au>
Committed: Tue Mar 14 21:09:07 2017 +1000
----------------------------------------------------------------------
src/spec/doc/core-semantics.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/groovy/blob/6aedd579/src/spec/doc/core-semantics.adoc
----------------------------------------------------------------------
diff --git a/src/spec/doc/core-semantics.adoc b/src/spec/doc/core-semantics.adoc
index 1baf68f..c2dd9a4 100644
--- a/src/spec/doc/core-semantics.adoc
+++ b/src/spec/doc/core-semantics.adoc
@@ -863,7 +863,7 @@ include::{projectdir}/src/spec/test/typing/OptionalTypingTest.groovy[tags=option
<2> we can still call the `toUpperCase` method, because the type of `aString` is resolved at runtime
So it doesn't matter that you use an explicit type here. It is in particular interesting when you combine this feature
-with <<typechecking,static type checking>>, because the type checker performs type inference.
+with <<static-type-checking,static type checking>>, because the type checker performs type inference.
Likewise, Groovy doesn't make it mandatory to declare the types of a parameter in a method:
@@ -1980,7 +1980,7 @@ discussed in a link:core-domain-specific-languages.html#section-delegatesto[spec
==== Dynamic vs static
-In the <<typechecking,type checking section>>, we have seen that Groovy provides optional type checking thanks to the
+In the <<static-type-checking,type checking section>>, we have seen that Groovy provides optional type checking thanks to the
`@TypeChecked` annotation. The type checker runs at compile time and performs a static analysis of dynamic code. The
program will behave exactly the same whether type checking has been enabled or not. This means that the `@TypeChecked`
annotation is neutral with regards to the semantics of a program. Even though it may be necessary to add type information