sberg added a comment.
Is it intended that a deleted copy assignment op as in `struct S { void
operator =(S &) = delete; };` (though, somewhat oddly, not in `struct S { void
operator =(S) = delete; };`) is now marked as trivial?
I think that's the root cause why a build of PDFium with clang-cl against the
MSVC standard library started to fail for me now, effectively complaining that
`__is_trivially_assignable(std::pair<int,int> &, std::pair<int,int> const &)`
is false (as expected) while `__has_trivial_assign(std::pair<int,int>)` is
(unexpectedly) true.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D127593/new/
https://reviews.llvm.org/D127593
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
