When mapping an optional value, if the value is <none> and followed
by comments, there will be a parsing error. This patch helps fix this
issue.
e.g.,
When mapping the following YAML,
Sections:
- Name: blah
Type: SHT_foo
Flags: [[FLAGS=<none>]] ## some comments.the raw value of ScalarNode is "<none> " rather than "<none>". We need
to remove the spaces.
This probably deserves a comment now.
Should we use rtrim(' ')? We do not need to trim the left side + trim by default trims too much it seems: " \t\n\v\f\r".