1. 16 Jul, 2020 2 commits
  2. 14 Jul, 2020 1 commit
  3. 06 Jul, 2020 1 commit
  4. 02 Jul, 2020 2 commits
  5. 29 Jun, 2020 1 commit
  6. 17 Jun, 2020 2 commits
  7. 15 Jun, 2020 2 commits
  8. 31 May, 2020 1 commit
  9. 23 May, 2020 1 commit
  10. 19 May, 2020 1 commit
  11. 12 May, 2020 1 commit
  12. 07 Feb, 2020 1 commit
  13. 21 Jan, 2020 1 commit
  14. 04 Aug, 2019 1 commit
  15. 17 Apr, 2019 1 commit
  16. 12 Mar, 2019 1 commit
  17. 21 Dec, 2018 1 commit
    • Simon Gene Gottlieb's avatar
      Fix float precision (#649) · abf941b2
      Simon Gene Gottlieb authored
      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.
      abf941b2
  18. 03 Sep, 2018 1 commit
  19. 28 Jan, 2018 1 commit
  20. 02 Dec, 2016 1 commit
  21. 12 Oct, 2016 1 commit
  22. 02 Apr, 2016 2 commits
  23. 26 Mar, 2016 1 commit
  24. 10 Jan, 2016 1 commit
  25. 29 Mar, 2015 1 commit
  26. 24 Jan, 2015 5 commits
  27. 24 Mar, 2014 4 commits
  28. 23 Mar, 2014 1 commit