Referencing other parameters results in out of order rendering

[jmthomas]

I use the ability to reference other parameters in conjunction with defining unique parameters. This works great for documenting inheritance chains. However, I've noticed that when doing this, the unique parameters are always rendered first in the documentation. I assume this is probably because of how you lookup the #see references and fill those in during another pass. Nothing serious but a little confusing because the parameter list doesn't match the method definition.

Steps to reproduce

class MyYard
  # @param value [String] The string
  def base(value); end
  # @param value (see #base)
  # @param value2 [String] The other string
  def base2(value, value2); end
end

Actual Output

Expected Output

Expected value to come before value2 in the parameter list.

Environment details:

• OS: [Windows 7]
• Ruby version 2.2.3
• YARD version 0.9.5

I have read the [Contributing Guide][contrib].
[contrib]: https://github.com/lsegal/yard/blob/master/CONTRIBUTING.md

[lsegal]

We could probably sort the params by their placement in the method signature, if provided. Patches accepted for this.

[jmthomas]

Opened PR #1065