Strange behavior with backticked javascript comments

[Acorn-zz]

`// ==UserScript==
// @version       1.0
// ==/UserScript==`

alert "hello world"

Gives

// ==UserScript==
// @version       1.0
// ==/UserScript==;alert("hello world");

---

`// ==UserScript==
// @version       1.0
// ==/UserScript==
`

alert "hello world"

Gives

// ==UserScript==
// @version       1.0
// ==/UserScript==
;alert("hello world");

(With an extraneous semicolon)

[breckinloggins]

This happens because inline JS is treated by the compiler as a Literal. The compiler doesn't know what's inside the JavaScript literal so it just assumes it's executable code (which it normally is).

To fix this, you'd have to parse the JavaScript itself, which would be a challenge and really only useful to solve this specific edge case.

[michaelficarra]

This looks like it should be a wontfix to me.

[satyr]

At least, literal → statement compilation is wrong.

$ coffee -bpe '0; 1; 2 if 3; 4; 5'
0;
1;if (3) {
  2;
}
4;
5;

There should be a newline after 1;.

[vendethiel]

Seems to be fixed, probably our @makeCode.