Don't use noSyntaxExpr for it. There is no good way to defensively case on that, nor is it clear one ought to do so.