search for: fmtlib

...at lists.llvm.org> wrote: > > I'm generally favorable on the core idea of having a type-safe and friendly format-string-like formatting utility I’m also generally in favour, but I wonder what the key motivations for designing our own, rather than importing something like FastFormat, fmtlib, or one of the other tried-and-tested C++ typesafe I/O libraries is. Has someone done an analysis of why these designs are a bad fit for LLVM, or are we just reinventing the wheel because we feel like it? David

...ully subsume its use cases, can we eventually get > that to be the name? > > (While I don't like streaming, I'm not trying to fight that battle here...) > > Also, you should probably look at what is quickly becoming a popular C++ > library in this space: https://github.com/fmtlib/fmt > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >

...ually > get > > that to be the name? > > > > (While I don't like streaming, I'm not trying to fight that battle > here...) > > > > Also, you should probably look at what is quickly becoming a popular C++ > > library in this space: https://github.com/fmtlib/fmt > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > -------------- next part -------------- An HTML attachment was sc...

...t; > > > I'm generally favorable on the core idea of having a type-safe and friendly format-string-like formatting utility > > > > I’m also generally in favour, but I wonder what the key motivations for designing our own, rather than importing something like FastFormat, fmtlib, or one of the other tried-and-tested C++ typesafe I/O libraries is. Has someone done an analysis of why these designs are a bad fit for LLVM, or are we just reinventing the wheel because we feel like it? > > (this keeps coming up in various contexts, so a somewhat longer/in-depth post than...

...ually > get > > that to be the name? > > > > (While I don't like streaming, I'm not trying to fight that battle > here...) > > > > Also, you should probably look at what is quickly becoming a popular C++ > > library in this space: https://github.com/fmtlib/fmt > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > _______________________________________________ > LLVM Develop...

...ually > get > > that to be the name? > > > > (While I don't like streaming, I'm not trying to fight that battle > here...) > > > > Also, you should probably look at what is quickly becoming a popular C++ > > library in this space: https://github.com/fmtlib/fmt > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > _______________________________________________ > LLVM Develop...

...ually > get > > that to be the name? > > > > (While I don't like streaming, I'm not trying to fight that battle > here...) > > > > Also, you should probably look at what is quickly becoming a popular C++ > > library in this space: https://github.com/fmtlib/fmt > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > _______________________________________________ > LLVM Develop...

A while back llvm::format() was introduced that made it possible to combine printf-style formatting with llvm streams. However, this still comes with all the risks and pitfalls of printf. Everyone is no-doubt familiar with these problems, but here are just a few anyway: 1. *Not type-safe.* Not all compilers warn when you mess up the format specifier. And when you're writing your own