Comment parser should handle tailing comment

[He-Pin]

Seems like the current parser did not handle the tailing comments,
like

{
#comment1
field1 #comment2
field2
}

here，#comment2 should be a tailing comment of field1,not a comment of field2

[OlegIlyenko]

Good catch, thanks for reporting! Field does have trailingComments, but looks like rendering algorithm puts them in a wrong place :)

[He-Pin]

no,it doesn't:)

[OlegIlyenko]

oops, looks like I jumped into conclusions too quickly. #comment2 looks in the right place, it's just assigned to a second field.

I think it would be a tricky to parse it in a way that preserves this information about comment placement, but let's see what I can do.

[He-Pin]

I think how about add a new field trailing:Boolean = false to the comment.
and add a new type of parser eg TrailingComment to the definition,and then try to parse it after a token,this type of Comment will end up with \nor \r\n`.