Same here, seems like some error that consistently generates 0 in multiple random tests and expects both true or false in different iterations of them.
if (value == 0) return false expects true and if (value == 0) return true expects false in those random tests
Same here, seems like some error that consistently generates 0 in multiple random tests and expects both true or false in different iterations of them.
if (value == 0) return false expects true and if (value == 0) return true expects false in those random tests
The first paragraph of the task kinda brings confusion and is unnecessary imo