Files
scryer-prolog/src/machine
Skgland 8aab887388 switch from Integer to u128
- u128 is only 16 bytes instead of 24
- incrementing u128 does not involve heap allocations
- u128 should be sufficent
 it would take more than 2 sextilion years to overflow if we would be incrementing it every tick at 5GHz
   i.e. 2^128-1 / 5 GHz / 60 / 60 / 24 / 356 > 2 sextilion

before this ~3.2% of the execution time of the program in https://github.com/mthom/scryer-prolog/issues/3265#issuecomment-4103176469 was spend in the increment_call_count function, after this change it's down to 0.3%
2026-03-21 13:36:40 +01:00
..
2026-01-10 18:13:59 +01:00
2025-07-07 22:02:27 -07:00
2025-08-01 19:08:02 +02:00
2026-02-20 22:45:09 +01:00
2026-01-14 20:39:48 -08:00
2026-03-21 13:36:40 +01:00
2025-07-07 22:38:10 -07:00
2026-01-10 18:13:59 +01:00
2026-03-21 13:36:40 +01:00
2026-03-21 13:36:40 +01:00
2025-07-07 22:38:10 -07:00
2026-01-10 18:13:59 +01:00
2026-03-21 13:36:40 +01:00
2025-07-07 22:38:10 -07:00