Tweak output of type params and constraints in the wrong order

[estebank]

r? @Centril @varkor

[estebank]

One thing to keep in mind is that we suggest fixing the order, but we don't proactively fix it, leading to situations like the following:

error: generic arguments must come before the first constraint
  --> file33.rs:11:34
   |
11 | struct Bar<'a, A, F: Foo<T = (), A, 'a, 4>> {
   |                          ------  ^  ^^  ^ generic argument
   |                          |       |  |
   |                          |       |  generic argument
   |                          |       generic argument
   |                          the constraint is provided here
   |
help: move the constraint after the generic arguments
   |
11 | struct Bar<'a, A, F: Foo<'a, A, 4, T = ()>> {
   |                         ^^^^^^^^^^^^^^^^^^

error[E0747]: lifetime provided when a constant was expected
  --> file33.rs:11:37
   |
11 | struct Bar<'a, A, F: Foo<T = (), A, 'a, 4>> {
   |                                     ^^
   |
   = note: constant arguments must be provided before lifetime arguments

error: aborting due to 2 previous errors

[varkor]

One thing to keep in mind is that we suggest fixing the order, but we don't proactively fix it, leading to situations like the following:

I think this is acceptable: it's still clear, just a little repetitive.

[Centril]

@bors r+

[bors]

📌 Commit 17a9523 has been approved by Centril

[bors]

⌛ Testing commit 17a9523 with merge d6ae20f50d7494dac10b3a779aa1014d7a40e0cf...

[Centril]

@bors retry

[bors]

⌛ Testing commit 17a9523 with merge af89eb5...