I think you may have misunderstood what I asked for. While None may not be entirely idiomatic in Python, I didn't actually ask that to be changed.
I asked for the return lines to be updated, part of the initial Python code that you see in the Solution editor pane when you start training. There, the comments claim that encode() and decode()only return str and I'm strongly suggesting that you want to add , or None when rejecting to those lines.
I also asked for the phrasing "rejected" to be clarified. That verb doesn't mean anything when it comes to a problem specification. Reject the value how? Please read my remarks on exceptions in Python in that light, I gave context to what I would normally have expected the problem to treat "rejecting" an input. Returning None is fine too here, but you need to make this explicit. This isn't something that you can simply bury with an excuse of this being an imperfect translation between different programming languages.
I note I'm not the only one to have reported this issue either, see this report, which could easily have been avoided if there wasn't this directly conflicting text that claims only str is to be returned.
Finally, and very ironically, dismissing feedback on your Kata with Broaden your horizons is incredibly close-minded. Learn to communicate better, being dismissive and rude is no way to treat anyone, especially not those that took the time to give you feedback.
No random tests
Testing could do with a touchup before approval.
All solution calls are run before all tests. Running tests immediately after a function call is much easier to debug.
Bump
humpf... XD
Not cleaned up, but forked anyway. Reraised on top.
This Haskell translation will clean up the description mess from the C++ translation as well.
Please reraise your issue.
Yeah, I'm pretty sure this is not a kata issue.
Why are you looking for
IZ_ZEROwhen the description specifiesIS_ZERO?IS_ZEROlooks to be there.now...:
x)
better do some other "double checking", I believe
I think you may have misunderstood what I asked for. While
Nonemay not be entirely idiomatic in Python, I didn't actually ask that to be changed.I asked for the
returnlines to be updated, part of the initial Python code that you see in the Solution editor pane when you start training. There, the comments claim thatencode()anddecode()only returnstrand I'm strongly suggesting that you want to add, or None when rejectingto those lines.I also asked for the phrasing "rejected" to be clarified. That verb doesn't mean anything when it comes to a problem specification. Reject the value how? Please read my remarks on exceptions in Python in that light, I gave context to what I would normally have expected the problem to treat "rejecting" an input. Returning
Noneis fine too here, but you need to make this explicit. This isn't something that you can simply bury with an excuse of this being an imperfect translation between different programming languages.I note I'm not the only one to have reported this issue either, see this report, which could easily have been avoided if there wasn't this directly conflicting text that claims only
stris to be returned.Finally, and very ironically, dismissing feedback on your Kata with Broaden your horizons is incredibly close-minded. Learn to communicate better, being dismissive and rude is no way to treat anyone, especially not those that took the time to give you feedback.
it is mentioned as of now
I promised that would be in
Preloaded, but it wasn't. I don't know how that happened.It's fixed now.
It seems
SUCCis defined in sample tests, but not in preloadedany idea why I get
ReferenceError: SUCC is not defined...?Loading more items...