### 🔎 Search Terms erasableSyntaxOnly ### 🕗 Version & Regression Information - This is the behavior in every version I tried including 6.0.3 ### ⏯ Playground Link https://www.typescriptlang.org/play/?erasableSyntaxOnly=true&ts=6.0.3#code/MYewdgziA2CmB00QHMAUBGABAak1ghhJmAK4C2ARrAE6YD0mATAJQDcAUJ50A ### 💻 Code ```ts //@erasableSyntaxOnly:true console.log(1 + 1 as number / 2); ``` ### 🙁 Actual behavior No error - which could lead a naive type-stripping compiler to incorrectly emit: ```ts console.log(1 + 1 / 2); ``` Though TypeScript itself correctly emits ```ts console.log((1 + 1) / 2); ``` ### 🙂 Expected behavior As there is no guaranteed room for `(`, it should error on this kind of `AsExpressions` and `SatisfiesExpressions` ### Additional information about the issue This issue was first discovered by @qnighy and reported as https://github.com/bloomberg/ts-blank-space/issues/62 It was since fixed to emit an error in: - [ts-blank-space](https://github.com/bloomberg/ts-blank-space/pull/63) v0.9.0 - [SWC](https://github.com/swc-project/swc/pull/11828) v1.15.40 - [Amaro](https://github.com/nodejs/amaro/releases/tag/v1.1.10) v1.1.10