This code is in time out about v HOT 10 OPEN

That screenshot is too dark for me to read, so I'm not sure what you're saying is the problem, there.

from v.

Yes, you need to update again.

from v.

Latest V is V 0.4.5 a1497c0. Your version is from 3 weeks ago, and is 132 commits behind the current.

Since V is still changing often, it is always best if you see an error to immediately do v up then check again. It may have already been fixed.

from v.

How much RAM do you have? I did start it with the higher number, and let it run for a couple of hours... still no output.

So I checked free memory, and saw it going down bit-by-bit over time. That's what happens with recursive routines like you have.

However, Ctrl-C stopped it immediately, no problem.

So I tried running with different numbers.

With 30000, I saw

0187500302      :30000

real    0m3.528s
user    0m3.544s
sys     0m0.044s

With 50000, it got much worse... as it in has been running over an hour, and hasn't finished, yet.

$ time v run edigit.v 50000
^CTerminated by signal  2 (SIGINT)

real    79m28.884s
user    79m19.146s
sys     0m6.845s
$

Quite a jump from 3.5 minutes to 1 hour 19 1/2 minutes for only 20000 more...

from v.

Try v up. It works for me on Manjaro with latest V:

...
6478007018      :24880
2766336227      :24890
9781045463      :24900
3113129404      :24910
4833570134      :24920
8695851652      :24930
6745951518      :24940
7680033395      :24950
5224105481      :24960
8176786777      :24970
2152798270      :24980
2501171958      :24990
1657760354      :25000
9               :25001[jalon@7950x ~]$ 

from v.

Hello,

i use the last version V 0.4.5 24af002.20fd795, I need to update again?

Thanks

from v.

In my arch linux, it's always a same problem

from v.

Latest V is V 0.4.5 a1497c0. Your version is from 3 weeks ago, and is 132 commits behind the current.

Since V is still changing often, it is always best if you see an error to immediately do v up then check again. It may have already been fixed.

I launch "v up" 3x or 4x times by day, so it's strange ;)

from v.

250001

Please try with 250001 not

Try v up. It works for me on Manjaro with latest V:

...
6478007018      :24880
2766336227      :24890
9781045463      :24900
3113129404      :24910
4833570134      :24920
8695851652      :24930
6745951518      :24940
7680033395      :24950
5224105481      :24960
8176786777      :24970
2152798270      :24980
2501171958      :24990
1657760354      :25000
9               :25001[jalon@7950x ~]$ 

Please try with 250001, on your capture you miss one 0

from v.

How much RAM do you have? I did start it with the higher number, and let it run for a couple of hours... still no output.

So I checked free memory, and saw it going down bit-by-bit over time. That's what happens with recursive routines like you have.

However, Ctrl-C stopped it immediately, no problem.

So I tried running with different numbers.

With 30000, I saw

0187500302      :30000

real    0m3.528s
user    0m3.544s
sys     0m0.044s

With 50000, it got much worse... as it in has been running over an hour, and hasn't finished, yet.

$ time v run edigit.v 50000
^CTerminated by signal  2 (SIGINT)

real    79m28.884s
user    79m19.146s
sys     0m6.845s
$

Quite a jump from 3.5 seconds to 1 hour 19 1/2 minutes for only 20000 more...

I have 16G ram , but go version is executed instantly, see time
Executed in 234.57 millis fish external
usr time 230.67 millis 197.00 micros 230.47 millis
sys time 80.87 millis 59.00 micros 80.81 millis

You can check here ; https://programming-language-benchmarks.vercel.app/problem/edigits

from v.