OP solved it, closing

Removed for now

It was already mentioned as an issue 3 months ago.

1st question: No ridesharing, each pickup and dropoff pair needs 1 taxi.
2nd question: A single batch of requests, the pickup and dropoff times indicate when the taxi should actually be in operation.

"not working correctly" how? Just checked, everything works for me.

You may basically have the correct idea, but suffer from an off-by-one error.

Go through your letter-to-value mapping carefully, and figure what overflow does exactly.

Look at the empty case also.

Marking as resolved.

Here's a simple way to prove 88 cannot exist in the example you gave:

There is only one instance of a possible 88, but it's preceded by ...201. The number 201 is not valid because it is outside your range, the number 01 cannot work because a non-zero integer cannot start with 0, and it cannot be 1 because that is outside your range. Thus it is proven that [10,88] is not a valid solution.

You need to provide the test case, your solution, and the expected solution in order for anybody to help you find what the problem is.

You can try printing the string argument to the screen (ie. the specific language's builtin stdout equivalent)

Hi,

Seems you're "rather new" to cw, so here are some general guidelines about the comments:

• Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
• Suggestions: well, I guess that part is clear
• Question anything else that is related to you having a problem solving a kata -> that's you, currently.

When you post issues:

• provide ALL the useful information:
  • language
  • input
  • outputs (actual expected) when relevant
  • error message when relevant
• check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
• if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)

When you post a question: well, most of the above apply too x)

When you post code, use proper github markdown, so that it's readable.

And for your current problem, since you don't provide any actually usable info... well... Closing since I'd rather bet on an error on your side, considering the number of completions. If you actually find/found an issue, feel free to open a fresh one, but with all the required information.

cheers

edit: warning with trailing spaces (" " or "\n")