Tabulation in <comments> blocks disrupts code clarity in parsed .xmir files

[SenjeyB]

Сomments often contain examples of code, but due to the lack of tabulation (or spaces in the start of the line) support in the block, the code in it cannot always be clearly restored while parsing .xmir files.

[yegor256]

@SenjeyB what exactly to do you suggest? Maybe you can formulate the bug report in the "expected-received" format?

[SenjeyB]

@yegor256

So the problem is that developers want to leave code examples in the code, but eolang is sensitive to line indentation like python:

# [] > foo
#   [] > @
#     inner.five > @
#   [] > inner
#     5 > five

And after parsing, you find in <comments> block like that:

...> foo\n[] > @\ninner.five > @\n[] > inner\n5 > five\n...

So in such situations it is not easy to say how much indentation to make.
Therefore, I would like to see an indication of the number of indents in this block (or indication of nesting depth of code blocks).
For examble adding \t escape sequences:

...> foo\n\t[] > @\n\t\tinner.five > @\n\t[] > inner\n\t\t5 > five\n...

[yegor256]

@SenjeyB this seems to be a problem of the parser, that skips the leading comments.

[0crat]

@SenjeyB Hey there, bug-hunter! 🐛 You just scored 8 points for your sharp eye! It's awesome how you're helping us level up our project quality. Keep that keen vision going - if you spot anything else in the repo that seems off, don't hold back. Report away and rack up those points! Every bug you catch is a win for the team. Keep 'em coming!