1. 01 Mar, 2020 4 commits
  2. 27 Feb, 2020 1 commit
  3. 26 Feb, 2020 1 commit
  4. 24 Feb, 2020 1 commit
  5. 23 Feb, 2020 1 commit
    • fghzxm's avatar
      Fix FMT_FORMAT_AS const specifier position (#1554) · 2161a73f
      fghzxm authored
      The current `FMT_FORMAT_AS` macro will make `formatter<Char *>::format`
      have the first argument type `const Char *&` which is incorrect an
      should be `Char *const &`.  This pull request fixes that by changing the
      first argument type in the macro definition body from `const Type &` to
      `Type const &`.
      2161a73f
  6. 21 Feb, 2020 1 commit
  7. 19 Feb, 2020 1 commit
  8. 15 Feb, 2020 1 commit
  9. 14 Feb, 2020 1 commit
  10. 10 Feb, 2020 1 commit
  11. 08 Feb, 2020 2 commits
  12. 07 Feb, 2020 1 commit
  13. 06 Feb, 2020 1 commit
  14. 01 Feb, 2020 1 commit
  15. 31 Jan, 2020 1 commit
  16. 30 Jan, 2020 1 commit
    • Milian Wolff's avatar
      Fix symbol visibility on Linux when compiling with -fvisibility=hidden (#1535) · 314e1500
      Milian Wolff authored
      Make FMT_API symbols use the default visibility on non-Windows
      platforms. Otherwise, one cannot use the generated fmt library when
      compiling globally with -fvisibility=hidden.
      
      Fixes compile errors like:
      
      ```
      ../3rdParty/fmt/include/fmt/core.h:757: error: undefined reference to 'fmt::v6::internal::assert_fail(char const*, int, char const*)'
      ```
      
      Note that the symbol exists, but is local:
      
      ```
      $ nm -C libfmtd.so.6.1.3  | grep assert_fail
                       U __assert_fail
      0000000000233ffa t fmt::v6::internal::assert_fail(char const*, int, char const*)
      ```
      
      With this patch, the compile error is gone and the symbol is properly
      exported:
      
      ```
      $ nm -a bin/libfmtd.so -C | grep assert_fail
                       U __assert_fail
      00000000002366ba T fmt::v6::internal::assert_fail(char const*, int, char const*)
      ```
      
      Change-Id: I96054e622d9a2ae81907e1b01a1033e629767a91
      314e1500
  17. 27 Jan, 2020 2 commits
  18. 24 Jan, 2020 1 commit
    • zeffy's avatar
      Fix formatting std::chrono::duration types to wide strings (#1533) · 1acb73f9
      zeffy authored
      * Fix formatting chrono durations to wide strings
      
      * Make format buffers const correct
      
      * Add FormatWide chrono test case
      
      * Fix incorrect wide encoding of 'µs'
      I think might be a source file encoding issue, so I used \u00B5 instead.
      
      * Update FormatWide test to use proper encoding of µs
      
      * Revert changes to format_localized's parameters
      
      * Use different overload of `std::time_put<T>::put` to avoid needing a format string
      
      * Use utf8_to_utf16 instead of having redundant overloads of get_units
      
      * Revert some minor changes
      
      * Remove FMT_CONSTEXPR from expression
      
      This should hopefully fix compilation on VS <2019
      
      * Make suggested changes from code review
      
      * Run clang-format on chrono.h
      
      * Make sure unit isn't null before constructing a string_view from it
      1acb73f9
  19. 23 Jan, 2020 3 commits
  20. 22 Jan, 2020 1 commit
    • Greg Sjaardema's avatar
      Fix so can work without locale defined · 25d6916b
      Greg Sjaardema authored
      If `FMT_STATIC_THOUSANDS_SEPARATOR` defined, then locale is not included or defined, so this call will be unresolved.  I think this is the correct fix based on the code in `format-inl.h` and `format.h`
      25d6916b
  21. 20 Jan, 2020 6 commits
  22. 19 Jan, 2020 2 commits
  23. 18 Jan, 2020 4 commits
  24. 17 Jan, 2020 1 commit