On 01.02.2016 22:27, Yury Selivanov wrote: > Right now they are private constants in ceval.c. > > I will (maybe) expose a private API via the _testcapi module to > re-define them (set them to 1 or 0), only to write better unittests. > I have no plans to make those constants public or have a public API to > tackle them. IMHO, this is something that almost nobody will ever use. Alright. I agree with you on that. What I actually meant was: how can we find the optimal values? I understand that 1000 and 20 are some hand-figured/subjective values for now. Is there standardized/objective way to find out the best values? What does best even mean here? Best, Sven
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4