Incorrect [deleted] specification in member list when some of the functions are deleted

[anarthal]

When some (but not all) of the functions are deleted, the function is rendered in the member list as deleted. This transmits that all functions are deleted, when they are not:

namespace boost::mysql {

struct move_only
{
    /// The copy assignment operator is deleted.
    move_only& operator=(const move_only&) = delete;

    /// Move assignment.
    move_only& operator=(move_only&&) = default;
};

}  // namespace boost::mysql

If the deleted function is not documented, the effects are more noticeable:

namespace boost::mysql {

struct move_only
{
    move_only& operator=(const move_only&) = delete;

    /// Move assignment.
    move_only& operator=(move_only&&) = default;
};

}  // namespace boost::mysql

I think the [deleted] specification would make more sense to be included only if all of the functions were deleted.

[anarthal]

Adding to this: it looks like the [deleted] specification is added only if the first member function in the overload list is deleted. The issue can be workarounded by moving the deleted function to not be the first one declared.