#25 ✓resolved
Thomas Han

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

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.

New-ticket 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

Shared Ticket Bins

People watching this ticket

Referenced by

Pages