[ 2019-09-23; Daniel adjusts wording to working draft changes ]

Due to the concept renaming caused by P1754R1 the proposed wording is outdated and needs adjustments.

This wording is relative to N4830, and also resolves LWG 3151.

1. Modify [concept.convertible] as indicated:

   -1- The convertible_to concept requires ana glvalue expression of a particular type and value category to be both implicitly and explicitly convertible to some other type. The implicit and explicit conversions are required to produce equal results.

   template<class From, class To>
     concept convertible_to =
       is_convertible_v<From, To> &&
       requires(add_rvalue_reference_t<From> (&f)()) {
         static_cast<To>(f());
       };
   

   -2- Let test be the invented function:

   To test(add_rvalue_reference_t<From> (&f)()) {
     return f();
   }
   

   for some types From and To, and let f be a function with no arguments and return type add_rvalue_reference_t<From> such that f() is equality-preserving. From and To model convertible_to<From, To> only if:

   1. (2.1) — To is not an object or reference-to-object type, or static_cast<To>(f()) is equal to test(f).

   2. (2.2) — add_rvalue_reference_t<From> is not a reference-to-object type, or

      1. (2.2.1) — If add_rvalue_reference_t<From> is an rvalue reference to a non const-qualified type, the resulting state of the object referenced by f() after either above expression is valid but unspecified ([lib.types.movedfrom]).

      2. (2.2.2) — Otherwise, the object referred to by f() is not modified by either above expression.