did you include last number?

Really, your code works fine with 1044388881413152506691752710716624382579964249047383780384233483283953907971557456848826811934997558340890106714439262837987573438185793607263236087851365277945956976543709998340361590134383718314428070011855946226376318839397712745672334684344586617496807908705803704071284048740118609114467977783598029006686938976881787785946905630190260940599579453432823469303026696443059025015972399867714215541693835559885291486318237914434496734087811872639496475100189041349008417061675093668333850551032972088269550769983616369411933015213796825837188091833656751221318492846368125550225998300412344784862595674492194617023806505913245610825731835380087608622102834270197698202313169017678006675195485079921636419370285375124784014907159135459982790513399611551794271106831134090584272884279791554849782954323534517065223269061394905987693002122963395687782878948440616007412945674919823050571642377154816321380631045902916136926708342856440730447899971901781465763473223850267253059899795996090799469201774624817718449867455659250178329070473119433165550807568221846571746373296884912819520317457002440926616910874148385078411929804522981857338977648103126085903001302413467189726673216491511131602920781738033436090243804708340403154190336 ?

I am skeptical of my rust code as I am new but I don't get the python error it's how is it my code that gives a time out I tested it in my pc and it works perfectly fine.

No problem :)

Rust and Python fork fixing a problem in reference solution.

OK, thanks for your work, sorry the forms. With the problem I have learned a lot about iterators, jaja. Thanks for that.

You are right, there is a problem. I've just published a new fork, I hope it's approved soon.

Good :) Now you know you need to find a radically different approach. Maybe it's better to focus more on the representation that on the number.

What needs to be fixed is your code. In Rust, line 6 causes an error; don't you guess what's happening? Your code in Python times out, it's your problem; translation was published two days ago, and 35 persons solved it without complaining.

Julia translation

I think that with that input, it will take a long time to be solved...

I tried with the input 123416523 and it took (37.97 secs, 74,454,731,984 bytes) to get the solution, which by the way is: 68961984

I see that this problem has exponential time to be solved, related to how big the input is...

• For example:
  • if the input is 12341652, it takes (3.81 secs, 6,917,976,752 bytes), but
  • an input which is one digit greater (fo example: 123416523) makes the solution time to go to (37.97 secs, 74,454,731,984 bytes)

We don't know what you are doing.

Maybe the random test are wrong or only I

If you don't know, why raise an issue?

All the random tests in Python (I assume you are using this language) just do this :

            test.assert_equals(nines(n), reference_solution(n), f"With n = {n}")

Just like fixed tests do stuff like this

        test.assert_equals(nines(3950), 1035, "With n = 3950")

Please be more specific, and however don't raise issues if you don't know.

Bruh this one this entirly broke first i get a error in rust thats not from my code "called Option::unwrap() on a None value at src/lib.rs:6:29"
and in python i get Execution Timed Out (12000 ms) please fix it.
both passes test but not in attempt