yes the while loop will break if the f0 is below or equal to 0 or if n becomes 0
or both so if the loop breaks by n becoming 0 then still the f0 is larger than 0 so true else if f0 becomes 0 or below the loop breaks and then if n is 0 returns true else false.
Why would anybody consider this a best practice? It's hard to read, way to complicated and not at all embracing the Kotlin language. This is Java style of the 90s...
you have encountered problem that had been already resolved - you are mutating the original array. What it means is you are probably passing a reference to an object rather than creating new, or making a shallow copy rather than deep one.
yes the while loop will break if the f0 is below or equal to 0 or if n becomes 0
or both so if the loop breaks by n becoming 0 then still the f0 is larger than 0 so true else if f0 becomes 0 or below the loop breaks and then if n is 0 returns true else false.
there is String.lines() for creating the stream since java 11
Why would anybody consider this a best practice? It's hard to read, way to complicated and not at all embracing the Kotlin language. This is Java style of the 90s...
I think this solution is harder to read than an inline if
Updated a fork to resolve description merge conflict
Merge conflict, update the description.
n=0??
i like this one :)
Did you post your comment on the wrong solution by accident? This solution is fine, one of the others has the problem you described.
oopsie
should be fixed by now - waiting for approval to my test cases updates
Made some updates on test cases for java solutions. Pls review :)
Approved
you have encountered problem that had been already resolved - you are mutating the original array. What it means is you are probably passing a reference to an object rather than creating new, or making a shallow copy rather than deep one.
Java translation kumited :)
Loading more items...