Unexpected trailing newlines in preprocessor nodes

[Wilfred]

Given the C code:

#include "foo.h"
#include "novel.h"


struct Bar {};

The parse tree produced is:

{Node translation_unit (0, 0) - (5, 0)}
  {Node preproc_include (0, 0) - (1, 0)}
    {Node #include (0, 0) - (0, 8)} "#include"
    {Node string_literal (0, 9) - (0, 16)}
      {Node " (0, 9) - (0, 10)} "\""
      {Node " (0, 15) - (0, 16)} "\""
    {Node '\n' (0, 16) - (1, 0)} "\n"
  {Node preproc_include (1, 0) - (4, 0)}
    {Node #include (1, 0) - (1, 8)} "#include"
    {Node string_literal (1, 9) - (1, 18)}
      {Node " (1, 9) - (1, 10)} "\""
      {Node " (1, 17) - (1, 18)} "\""
    {Node '\n' (1, 18) - (4, 0)} "\n\n\n"
  {Node struct_specifier (4, 0) - (4, 13)}
    {Node struct (4, 0) - (4, 6)} "struct"
    {Node type_identifier (4, 7) - (4, 10)} "Bar"
    {Node field_declaration_list (4, 11) - (4, 13)}
      {Node { (4, 11) - (4, 12)} "{"
      {Node } (4, 12) - (4, 13)} "}"
  {Node ; (4, 13) - (4, 14)} ";"

Note that the second preproc_include looks like it includes all the trailing newlines.

[maxbrunsfeld]

I agree; it'd be better to not have the trailing newline as part of the node.