1. 11 Oct, 2019 1 commit
  2. 05 Oct, 2019 1 commit
  3. 04 Oct, 2019 1 commit
  4. 02 Oct, 2019 6 commits
  5. 27 Sep, 2019 4 commits
  6. 25 Sep, 2019 1 commit
  7. 15 Sep, 2019 3 commits
  8. 10 Sep, 2019 3 commits
  9. 04 Aug, 2019 1 commit
  10. 17 Apr, 2019 1 commit
  11. 24 Mar, 2019 2 commits
  12. 13 Mar, 2019 1 commit
  13. 12 Mar, 2019 1 commit
  14. 27 Feb, 2019 1 commit
  15. 13 Feb, 2019 1 commit
  16. 06 Jan, 2019 1 commit
  17. 21 Dec, 2018 1 commit
    • Fix float precision (#649) · abf941b2
      The issue is that numbers like
      2.01 or 3.01 can not be precisely represented with binary floating point
      numbers.
      
      This replaces all occurrences of 'std::numeric_limits<T>::digits10 + 1' with
      'std::numeric_limits<T>::max_digits10'.
      
      Background:
      Using 'std::numeric_limits<T>::digits10 + 1' is not precise enough.
      Converting a 'float' into a 'string' and back to a 'float' will not always
      produce the original 'float' value. To guarantee that the 'string'
      representation has sufficient precision the value
      'std::numeric_limits<T>::max_digits10' has to be used.
      Simon Gene Gottlieb committed
  18. 23 Nov, 2018 1 commit
  19. 19 Nov, 2018 1 commit
  20. 18 Nov, 2018 1 commit
  21. 25 Sep, 2018 1 commit
  22. 23 Sep, 2018 1 commit
  23. 06 Sep, 2018 1 commit
  24. 04 Sep, 2018 1 commit
  25. 03 Sep, 2018 3 commits