Anonymous
7/14/2025, 5:05:50 PM No.105903435
What is the biggest number you can use with your favorite programming language on your Science Computer?
Replies:
Thread 105903435 - /g/ [Archived: 438 hours ago]
Anonymous
7/14/2025, 5:21:15 PM No.105903587
P A D D I N G
A
D
D
I
N
G
A
D
D
I
N
G
Anonymous
7/14/2025, 5:29:51 PM No.105903665
>>105903435 (OP)
> (fac 1 5000)
4228577926605543522201064200233584405390786674626646748849782402181358052 7081082006908990478717063875370847466573006854458784860666838127363372108 9377278763127939036305846216064390447898698223987192970889621161265296832
it just continues for 16338 digits
> (fac 1 5000)
4228577926605543522201064200233584405390786674626646748849782402181358052 7081082006908990478717063875370847466573006854458784860666838127363372108 9377278763127939036305846216064390447898698223987192970889621161265296832
it just continues for 16338 digits
Replies:
Anonymous
7/14/2025, 5:34:56 PM No.105903726
>>105903665
>16338 digits
This is a fairly small number. Can the language not handle bigger or do you just find this specific number interesting? Also, what flavor of LISP is this?
>16338 digits
This is a fairly small number. Can the language not handle bigger or do you just find this specific number interesting? Also, what flavor of LISP is this?
Replies:
Anonymous
7/14/2025, 5:36:22 PM No.105903741
You're a waste of space maidfag
Fuck you and your parents for giving you internet access when you should be locked up in a facility
Fuck you and your parents for giving you internet access when you should be locked up in a facility
Anonymous
7/14/2025, 5:43:20 PM No.105903808
>>105903726
>This is a fairly small number. Can the language not handle bigger or do you just find this specific number interesting? Also, what flavor of LISP is this?
It was just arbitrarily selected, (fac 1 100000) is apparently 456574 digits starting with 2824229407960347874293421578024535518477494926091224850578918086542977950901063
>Also, what flavor of LISP is this?
chez scheme where fac is (define (fac a n) (if (= n 0) a (fac (* a n) (- n 1))))
>This is a fairly small number. Can the language not handle bigger or do you just find this specific number interesting? Also, what flavor of LISP is this?
It was just arbitrarily selected, (fac 1 100000) is apparently 456574 digits starting with 2824229407960347874293421578024535518477494926091224850578918086542977950901063
>Also, what flavor of LISP is this?
chez scheme where fac is (define (fac a n) (if (= n 0) a (fac (* a n) (- n 1))))
Replies:
Anonymous
7/14/2025, 5:43:47 PM No.105903816
>>105903435 (OP)
i am sorry i have seen big numbers in bc and made calcs with bc that output is too big for haswell and bash
i am sorry i have seen big numbers in bc and made calcs with bc that output is too big for haswell and bash
Anonymous
7/14/2025, 5:48:59 PM No.105903866
>>105903808
Thank you for telling me. This is interesting. Can you make it do one which is one billion digits long? What is the performance like? Can it do ten billion digits? Your maid is very pretty.
Thank you for telling me. This is interesting. Can you make it do one which is one billion digits long? What is the performance like? Can it do ten billion digits? Your maid is very pretty.
Replies:
Anonymous
7/14/2025, 6:29:31 PM No.105904227
>>105903866
Probably, but I've only reach 5 million (5565709) so far
> (time (fac 100000))
191 collections
8.970057500s elapsed cpu time, including 0.031200200s collecting
9.023377915s elapsed real time, including 0.024942610s collecting
9944222800 bytes allocated, including 9939380528 bytes reclaimed
456574
> (time (fac 1000000))
2000 collections
1269.177335700s elapsed cpu time, including 18.766920300s collecting
1275.942481429s elapsed real time, including 18.749773468s collecting
1200827529008 bytes allocated, including 1200735143232 bytes reclaimed
5565709
The memory use graph for this was interesting, after a series of initial 2gb spikes it flatlined until the end
Probably, but I've only reach 5 million (5565709) so far
> (time (fac 100000))
191 collections
8.970057500s elapsed cpu time, including 0.031200200s collecting
9.023377915s elapsed real time, including 0.024942610s collecting
9944222800 bytes allocated, including 9939380528 bytes reclaimed
456574
> (time (fac 1000000))
2000 collections
1269.177335700s elapsed cpu time, including 18.766920300s collecting
1275.942481429s elapsed real time, including 18.749773468s collecting
1200827529008 bytes allocated, including 1200735143232 bytes reclaimed
5565709
The memory use graph for this was interesting, after a series of initial 2gb spikes it flatlined until the end