preserve_annotations changes position of /* #__PURE__ */ comments in function calls

[justin-schroeder]

Bug report

When using inline arrow functions as function call arguments and those functions utilize the /* #__PURE__ */ annotation, the annotation is moved to an invalid location (downstream this results in rollup warnings and suboptimal tree shaking).

Version (complete output of terser -V or specific git commit)

v5.31

Complete CLI command or minify() options used

{
  format: {
    preserve_annotations: true
  }
}

terser input

export function x(a,b) {}

const nestedStatement = () => /* #__PURE__ */ x(() => 'foo', /* #__PURE__ */ x('a', 'b'));

export const foobar = nestedStatement()

terser output or error

export function x(o,t){}export const foobar=/* #__PURE__ */x((()=>"foo"/* #__PURE__ */),x("a","b"));

Expected result

export function x(o,t){}export const foobar=/* #__PURE__ */x((()=>"foo"), /* #__PURE__ */ x("a","b"));

[fabiosantoscode]

I'm pretty sure these comments are being attached to the wrong node at the input 🤔

Maybe this isn't the best approach. Maybe annotations should be reconstructed as opposed to preserved.