Ignoring overloads after the first in method comments

[euglena1215]

Description

When using #:: comments to express method overloads, everything after the first | is ignored.

Steps to Reproduce

Run rbs-inline on the following program:

#:: (String) -> String | (Integer) -> Integer
def foo(x)
  x
end

Expected Result

The following should be generated:

#:: (String) -> String | (Integer) -> Integer 
def foo: (String) -> String | (Integer) -> Integer

Actual Result

Everything after the first | is ignored, resulting in:

#:: (String) -> String | (Integer) -> Integer 
def foo: (String) -> String

Environment

• rbs-inline: 0.3.0

[soutaro]

The syntax accepts only one overload. So, having another overload after the | token doesn't work.

[ParadoxV5]

Is this the current way to write overloads?

#:: (String) -> String
#:: (Integer) -> Integer

Perhaps OP’s expectation is more explicit?

#:: (String) -> String
# | (Integer) -> Integer

[soutaro]

Hmm...
Yeah, it's possible.

[euglena1215]

Oh, thank you very much. It seems to work as expected with the following.

#:: (String) -> String
#:: (Integer) -> Integer

I also found the following on the Wiki:

Having multiple #:: syntax generates method definition with overloads.

My issue was not so much a syntax problem, but rather that I felt rbs-inline could not express overloads. I will close this issue now that I know I was mistaken.

Thank you for your comments!