This looks like a duplicate of the Basic Calculator kata.
nitpick: minor typo in the description indivi[DU]al
indivi[DU]al
nitpicks: minor typos in the description
.. start compa[]ring from .. .. also aster[OI]ds in ..
nitpick: minor typo in the description.
five thousand cups wi[T]hout being DEAD
A minor typo in the description:
... the 1st character of the ou[T]put is the average ...
I'd say drop maxTest from sample as it reveals the solution. Having testSimpleCases alone should be enough to start the challenge.
maxTest
testSimpleCases
nitpick: a minor typo in the description damage rec[EI]ved
damage rec[EI]ved
A few minor typos in the description:
nitpick: a minor typo in the description the symbol[_]s in the top row.
the symbol[_]s in the top row
nitpick: a minor typo in the description string conta[IN]ing.
string conta[IN]ing
nitpick: a minor typo in the description your succes[S]ful algorithm.
your succes[S]ful algorithm
nitpick: a minor typo in the description are identical there[A]fter..
are identical there[A]fter.
This comment is hidden because it contains spoiler information about the solution
Shall we follow camel-case Java naming conventions here?
DiagonalProduct.[r]eturnProduct()
Any particular reason for using Boolean[] over primitive boolean[]?
Loading collection data...
This looks like a duplicate of the Basic Calculator kata.
nitpick: minor typo in the description
indivi[DU]al
nitpicks: minor typos in the description
nitpick: minor typo in the description.
A minor typo in the description:
I'd say drop
maxTest
from sample as it reveals the solution. HavingtestSimpleCases
alone should be enough to start the challenge.nitpick: a minor typo in the description
damage rec[EI]ved
A few minor typos in the description:
nitpick: a minor typo in the description
the symbol[_]s in the top row
.nitpick: a minor typo in the description
string conta[IN]ing
.nitpick: a minor typo in the description
your succes[S]ful algorithm
.nitpick: a minor typo in the description
are identical there[A]fter.
.This comment is hidden because it contains spoiler information about the solution
Shall we follow camel-case Java naming conventions here?
Any particular reason for using Boolean[] over primitive boolean[]?
Loading more items...