Andrey Semashev
Andrey Semashev
> `BOOST_TEST_EQ` tests for equality using ==, which for char* compares addresses, so the output also prints addresses to match that. In Boost.Filesystem case we are comparing `path` with string...
I think, the special case is comparing two pointers and the rest can be assumed to operate as intended (i.e. there must be a user-defined comparison or conversion operator for...
Also, the comparison logic is unrelated to output formatting, which is what this issue about.
Looks like `copysign` is defined as a macro somewhere, possibly in the Python headers. If that's the case, Python should be fixed, IMHO.
It might also be useful to add a workaround to Boost.Python. CC @stefanseefeld.
It is not obvious as to what the behavior should be when the size of the source and target types are different. And such a behavior would likely be endian-dependent....
I don't understand what's this about. Closing as spam. @vinniefalco Please be clear about the problem description in future issues and avoid jargonisms.
It requires quite a bit more work than just adding a pragma. One needs to also scan through other Boost libraries (and their tests) and create PRs updating includes. I'm...
> > It requires quite a bit more work than just adding a pragma > > Yeah well, I bet that after the pragma ships for a few releases, those...
> I feel _very_ strongly that the arguments to `pointer_in_range` — like the arguments to `rotate` and so on (with the notable, regrettable, exception of `std::clamp`) — should be given...