search for: abseil

...ement C++17 `std::char_traits` [4]. This means that any usage of `std::string_view` in a constant expression has the possibility to break. `__builtin_constant_p` may be rare, but `std::string_view` is not. This regression was first found because it breaks `absl::StrFormat` [4]. This bug will break Abseil's LTS w/ libstdc++. Abseil cannot fully work around this bug. I would implore us to fix this bug in the upcoming 8 release. /Eric [1] https://reviews.llvm.org/D59038 [2] https://godbolt.org/z/VOCCJF [3] https://github.com/abseil/abseil-cpp/issues/271 [4] https://github.com/gcc-mirror/gcc/blo...

...ns that any usage of `std::string_view` in >> a constant expression has the possibility to break. `__builtin_constant_p` >> may be rare, but `std::string_view` is not. >> >> This regression was first found because it breaks `absl::StrFormat` [4]. >> This bug will break Abseil's LTS w/ libstdc++. Abseil cannot fully work >> around this bug. >> >> I would implore us to fix this bug in the upcoming 8 release. >> >> /Eric >> >> [1] https://reviews.llvm.org/D59038 >> [2] https://godbolt.org/z/VOCCJF >> [3] https://git...

Hi, I am using the llvm libraries compiled with the C++14 standard with a host application that is compiled with the C++17 standard (Both on Windows/MSVC). I am running into an incompatibility for which I filed a bug report: https://bugs.llvm.org/show_bug.cgi?id=44131 However, I was wondering if C++17 host applications are even supported? Regards, Machiel van Hooren

...es > that have "here's the default vector you shuold use instead of > std::vector for these reasons" situations). > I had looked into this when the revision was sent, but I couldn't find a library with a "vector with inlined storage" and a default N value. Both Abseil and Folly have a SmallVector equivalent, Abseil does not have a default: https://github.com/abseil/abseil-cpp/blob/master/absl/container/inlined_vector.h#L69-L71 Folly has a default hard-coded to 1: https://github.com/facebook/folly/blob/master/folly/small_vector.h#L430 Folly has also another class...

...or you shuold use instead of >>> std::vector for these reasons" situations). >>> >> >> I had looked into this when the revision was sent, but I couldn't find a >> library with a "vector with inlined storage" and a default N value. >> Both Abseil and Folly have a SmallVector equivalent, Abseil does not have >> a default: >> https://github.com/abseil/abseil-cpp/blob/master/absl/container/inlined_vector.h#L69-L71 >> Folly has a default hard-coded to 1: >> https://github.com/facebook/folly/blob/master/folly/small_vector...

...e's the default vector you shuold use instead of >> std::vector for these reasons" situations). >> > > I had looked into this when the revision was sent, but I couldn't find a > library with a "vector with inlined storage" and a default N value. > Both Abseil and Folly have a SmallVector equivalent, Abseil does not have > a default: > https://github.com/abseil/abseil-cpp/blob/master/absl/container/inlined_vector.h#L69-L71 > Folly has a default hard-coded to 1: > https://github.com/facebook/folly/blob/master/folly/small_vector.h#L430 > Fol...

On Aug 10, 2018, at 9:35 PM, Eric Fiselier <eric at efcs.ca> wrote: > > Part of me is still concerned with the future, and the filesystems which are yet to exist. > Me too. But it is best to target modern systems when targeting future systems adds an unnecessary cost. When future systems come into being, it is likely because future hardware is making those future systems

On Mon, Nov 16, 2020 at 2:12 PM David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Nov 16, 2020 at 1:55 PM Mehdi AMINI <joker.eph at gmail.com> wrote: > > On Mon, Nov 16, 2020 at 12:55 PM David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> I will say I'm not a huge fan of adding even more names for things in > >> this fairly