https://issues.dlang.org/show_bug.cgi?id=24848

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |pull

--- Comment #1 from Dlang Bot <dlang-bot@dlang.rocks> ---
@ntrel created dlang/dmd pull request #17055 "Fix Bugzilla 24848 - bad parser diagnostic for a partial MulExp" fixing this issue:

- Fix Bugzilla 24848 - bad parser diagnostic for a partial MulExp

https://github.com/dlang/dmd/pull/17055

--

https://issues.dlang.org/show_bug.cgi?id=24848

Nick Treleaven <nick@geany.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nick@geany.org

--- Comment #2 from Nick Treleaven <nick@geany.org> ---
> In no way we multiply by zero.

This happens for pretty much any binary expression, the pull fixes that. This is the main bug IMO.

> Second the closing right paren is there.

I think there are many cases where subsequent parser error messages are confusing.

--

https://issues.dlang.org/show_bug.cgi?id=24848

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/dmd pull request #17055 "Fix Bugzilla 24848 - bad parser diagnostic for a partial MulExp" was merged into master:

- 5d01f144e2cc63a9c1c0edd5ab954a8edac11403 by Nick Treleaven:
  Fix Bugzilla 24848 - bad parser diagnostic for a partial MulExp

https://github.com/dlang/dmd/pull/17055

--