Rezultati pretraživanja
  1. 26. lip 2019.
    Prikaži ovu nit
  2. 25. lip 2019.

    Three reasons to use . See the right column.

    Prikaži ovu nit
  3. 28. svi 2019.
    Odgovor korisniku/ci

    Nice, successfully ran a 'hello world' using header-only version of . Compile time is still a limitation to test longer codes though. Congrats.

  4. 21. ruj 2018.
  5. 10. stu 2018.

    Seems like there is a good chance and you'll get your wish in C++20!

  6. 26. lip 2019.

    But seems like MinGW is not supported for ... :(

    Prikaži ovu nit
  7. oss-fuzz integration has been merged into {fmt}: Thanks to !

  8. Created the [fmt] tag on StackOverflow for questions about {fmt} and the text formatting proposal:

    Prikaži ovu nit
  9. 21. ruj 2018.
  10. 29. ruj 2018.

    Seems like I should use instead of std::to_string. Values formatting is the one of the current bottleneck...

  11. Precompiled format strings aka the biggest PR in the history of {fmt} =)

  12. Chrono formatting in {fmt} is getting more sophisticated.

  13. {fmt} support has been added to oss-fuzz, a continuous fuzzing system for open-source software. Thanks who has done all the work to make this happen!

  14. corollary: Reading the cmake source code, I think it has the chance of reducing like 10% or something large by moving away from std::stringstream to 🔥🔥🔥 i feel like, i know more cmake now than i would like. ha.

    Prikaži ovu nit
  15. 24. velj 2018.

    For lots of small/mid-size using , there is observable gain in using preallocated std::string of static size, to ensure subsequent fmt::Buffer::grow() calls never reallocate

  16. 6. stu 2017.

    RT : New blog post: "Compile-time format string checks"

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.