tighten wording

Author: zth

compiler/ml/error_message_utils.ml

@@ -388,16 +388,10 @@ let print_extra_type_clash_help ~extract_concrete_typedecl ~env loc ppf
          @,\
          Possible solutions: @,\
          - These types are compatible at runtime. You can use the coercion \
-         operator @{<info>:>@} to convert to the expected type @{<info>%s@}."
-        target_type_string;
+         operator to convert to the expected type";
       match suggested_rewrite with
-      | Some rewrite ->
-        fprintf ppf
-          "@,\
-          \  If you want to use coercion, rewrite the highlighted code to: \
-           @{<info>%s@}@,"
-          rewrite
-      | None -> ())
+      | Some rewrite -> fprintf ppf ": @{<info>%s@}@," rewrite
+      | None -> fprintf ppf ": @{<info>:>@}@,")
   | _ -> ()
 
 let type_clash_context_from_function sexp sfunct =

tests/build_tests/super_errors/expected/subtype_record.res.expected

@@ -11,6 +11,5 @@
   But this function argument is expecting: SomeModule.someType
 
   Possible solutions: 
-  - These types are compatible at runtime. You can use the coercion operator :> to convert to the expected type SomeModule.someType.
-    If you want to use coercion, rewrite the highlighted code to: (v :> SomeModule.someType)
+  - These types are compatible at runtime. You can use the coercion operator to convert to the expected type: (v :> SomeModule.someType)
 

tests/build_tests/super_errors/expected/subtype_string.res.expected

@@ -11,6 +11,5 @@
   But it's expected to have type: string
 
   Possible solutions: 
-  - These types are compatible at runtime. You can use the coercion operator :> to convert to the expected type string.
-    If you want to use coercion, rewrite the highlighted code to: (One :> string)
+  - These types are compatible at runtime. You can use the coercion operator to convert to the expected type: (One :> string)