chained methods do no parse correctly if . is separated from call

[sredrv]

Describe the feature

V currently supports, method chaining in single-line, as below.

	mut s:= 'aAabBc'
	s = s.camel_to_snake().to_lower().to_upper()

I want V to support, methods specified on more than one line:

	mut s:= 'aAabBc'
	s = s.  camel_to_snake().
                 to_lower().
                 to_upper()

Use Case

Readability issue, when more custom built methods are used.

Proposed Solution

V language parser needs to be enhanced

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Version used

V 0.4.9

Environment details (OS name and version, etc.)

OS Linux

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

[JalonSolov]

The code works as expected if you move the .s to the front of each call (no spaces between), as in

        mut s:= 'aAabBc'
        s = s   .camel_to_snake()
                .to_lower()
                .to_upper()
        println(s)

which gives the output

A_AAB_BC

Now, whether or not it should be considered an error with the . at the end, I don't know.

[JalonSolov]

At the very least, the error messages could be cleaned up a LOT, to better convey what's wrong. Here's what you get currently:

x.v:2:10: error: `string` has no property ``
    1 |     mut s:= 'aAabBc'
    2 |     s = s.  camel_to_snake().
      |             ~~~~~~~~~~~~~~~~~
    3 |                  to_lower().
    4 |                  to_upper()
x.v:2:4: error: assignment mismatch: 1 variable 0 values
    1 |     mut s:= 'aAabBc'
    2 |     s = s.  camel_to_snake().
      |       ^
    3 |                  to_lower().
    4 |                  to_upper()
x.v:3:18: error: unknown function: to_lower
    1 |     mut s:= 'aAabBc'
    2 |     s = s.  camel_to_snake().
    3 |                  to_lower().
      |                  ~~~~~~~~~~
    4 |                  to_upper()
x.v:3:18: error: `to_lower()` does not return a value
    1 |     mut s:= 'aAabBc'
    2 |     s = s.  camel_to_snake().
    3 |                  to_lower().
      |                  ~~~~~~~~~~~
    4 |                  to_upper()
x.v:4:18: error: unknown function: to_upper
    2 |     s = s.  camel_to_snake().
    3 |                  to_lower().
    4 |                  to_upper()
      |                  ~~~~~~~~~~

[sredrv]

The code works as expected if you move the .s to the front of each call (no spaces between), as in

I am ok, with the latest parser support, with the syntax you mentioned.

At the very least, the error messages could be cleaned up a LOT, to better convey what's wrong.

Sure, just, get the error messages cleaned up.

It is the same issue, for one error, we get multiple messages, throughout the V compiler.
Such a clean-up, would be a very big Welcome FIX.