The only reasons we keep those factors as ints rather than floats are:

  1. We can't change the struct fields in 2.4.x
  2. The rationale that int based operations will "always"
     be faster than floating point

2.5.0 doesn't suffer from #1. We can break API/ABI if there's
a good reason. And #2 is open for debate :)

But yes, the extra granularity (dynamic range) of ldfactor
now means it may take longer to reach steady state for
some methods. We could use the 'age' method to maybe adjust
for that...

Reply via email to