Precondition (@Requires) should be checked before the method, closure is invoked
Reported by Thomas Han | May 18th, 2011 @ 09:47 AM | in 1.2.4
The converse is true for the post conditions (@Ensures).
The check should be after the the method, closure invocation.
class G {
String g
}
class H {
@Requires({ g != null })
static void h(G g) {
g.g
}
}
if you call H.h(null) it will fail with a null pointer exception instead of AssertionViolation (more specifically PreconditionViolation)
Comments and changes to this ticket
-
me (at andresteingress) May 18th, 2011 @ 11:10 AM
- Milestone set to “1.2.3”
- Assigned user set to “me (at andresteingress)”
- Milestone order changed from “3” to “0”
a duplicate of #10
-
me (at andresteingress) May 18th, 2011 @ 11:16 AM
- Milestone changed from “1.2.3” to “1.2.4”
- Milestone order changed from “8” to “0”
-
me (at andresteingress) May 30th, 2011 @ 12:38 PM
- Milestone order changed from “1” to “0”
(from [4b7cc2161b9ff744c368aaea0a476a0d07475cd7]) fixed [#10] Support for static methods, fixed [#25] Precondition (@Requires) should be checked before the method, closure is invoked https://github.com/andresteingress/gcontracts/commit/4b7cc2161b9ff7...
-
me (at andresteingress) May 30th, 2011 @ 12:40 PM
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
core module
People watching this ticket
me (at andresteingress)
Referenced by
-
25
Precondition (@Requires) should be checked before the method, closure is invoked
(from [4b7cc2161b9ff744c368aaea0a476a0d07475cd7])
fixed [...
-
10
Support for static methods
(from [4b7cc2161b9ff744c368aaea0a476a0d07475cd7])
fixed [...