missing return causes wrong method behavior
Reported by me (at andresteingress) | April 11th, 2011 @ 11:00 AM | in 1.2.2
whenever an invariant is applied on some sort of the following method, the generated code calls the last statement twice
def pop() {
elements.pop() }
vs.
def pop() {
return elements.pop() }
Comments and changes to this ticket
-
-
me (at andresteingress) April 14th, 2011 @ 11:14 AM
- State changed from “new” to “resolved”
has been resolved due to work done in [#19]
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
-
16
missing return causes wrong method behavior
(from [6a8a09ef78b5761337a9d594e22ffb726e9918f6])
test-ca...