Don't worry no offense taken. Please remember that most of Kotlin users are Java newcomers, I could have provided in the tests calls to non null values, but I wanted them to use the nullabillity inference operators
I'll revert it, since it's one of the language features to provide new symbols to deal against million dollar error, and make nullability inferences at compile time. This is NOT an issue, you could have asked instead of reporting.
An empty list has a length of 0, meaning it will go for the else statement and will keep returning an empty list. This will repeat forever leading to a stackoverflow.
it seems to have been fixed
Not an issue. Everything is preloaded and accessible after you complete the kata.
Don't worry no offense taken. Please remember that most of Kotlin users are Java newcomers, I could have provided in the tests calls to non null values, but I wanted them to use the nullabillity inference operators
I'll revert it, since it's one of the language features to provide new symbols to deal against million dollar error, and make nullability inferences at compile time. This is NOT an issue, you could have asked instead of reporting.
This comment is hidden because it contains spoiler information about the solution
Happy to help :)
An empty list has a length of 0, meaning it will go for the else statement and will keep returning an empty list. This will repeat forever leading to a stackoverflow.