jyknight wrote:

> This might not actually be fixed in the latest boost::mpl.  

Hm, indeed. It seems that the 
"[trick](https://github.com/boostorg/mpl/issues/69#issuecomment-1316152037)" 
they used to solve it in mpl indeed was fixed/obsoleted by this change -- the 
trick no longer avoids the error. Sorry, I didn't realize that their fix was 
depending on a bug in Clang!

However -- I haven't actually seen _any_ problems caused by this commit, when 
using an up-to-date version of Boost! I believe that's because just about 
nothing actually uses `boost::mpl::integral_c`. The boost fix which _actually 
matters_ to real-world code was that boost numeric_conversion was [changed to 
stop 
using](https://github.com/boostorg/numeric_conversion/commit/50a1eae942effb0a9b90724323ef8f2a67e7984a)
 `boost::mpl::integral_c`. And that fix is still operational!

So...I wonder if it maybe does not really matter that MPL's integral_c is 
broken again, if it's not really impacting anything. It'd be great if some 
expert could help them craft a _correct_ fix to the type, of course...

https://github.com/llvm/llvm-project/pull/143034
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to