Option "--lineDir:on" may mess up code in `emit` pragma

[MednauN]

Nim version 0.17.2 (from commit 811fbda)

That's quite unusual issue, but I caught it today in our project.
Here's the sample code:

proc f(): int32 =
  {.emit: """
    #if 1
    `result` = 1;
    #endif
  """.}

echo f()

The important part here is that code inside emit begins with a C preprocessor directive. If you compile this code with command
nim c --lineDir:on test.nim
compiler produces following C code:

N_NIMCALL(NI32, f_nihCtddZTotXPkpuYzTLdQ)(void) {
	NI32 result;	nimfr_("f", "test.nim");	result = (NI32)0;
#line 3 "C:\\projects\\temp\\test.nim"
	nimln_(3, "test.nim");	    #if 1
    result = 1;
    #endif
  
	popFrame();	return result;}

As you can see, first line break before #if 1 is somehow removed and #if 1 goes to the same line as nimln_. Well, and this code doesn't compile since preprocessor directives should start with a new line.

[MednauN]

Apparently, there is similar closed issue #5989 for --debugger:native switch.

[jxy]

I don't think #5989 is fixed, but I can't reopen that issue.

For now, use --debugger:native --lineDir:off helps.

[ringabout]

You can keep an empty line by yourself

proc f(): int32 =
  {.emit: """

    #if 1
    `result` = 1;
    #endif
  """.}

echo f()

nim c --lineDir:on -r ttest.nim
1

[ringabout]

The workaround is good enough and hard to fix.

[ringabout]

I don't think #5989 is fixed,

c446806

[jxy]

Shouldn't we leave the bug open, or at least make it something like won't fix? Anybody try to debug nim code while emitting C preprocessor directive would trip on this. A good enough workaround is not equal to a proper fix.