Comment author: @garrigue

This is originally designed to avoid any syntactic conflict between the core and module levels.
I see at least two way it could be improved:

• By allowing to omit the parenthesis where there is no (potential) ambiguity, i.e. everywhere except functor positions.
  In theory it's ok, but one would have to fix the conflicts by hand. Painful.
• Just remove the need for double parentheses.
  I.e. create a paren_module_expr non-terminal, which can be used directly as argument to a functor.

The second option is much simpler. I include a patch that seems to work.

Comment author: @sliquister

I ran into this issue of having to write double parens again. Any chance this patch can be merged? The patch looks good to me (the error case that's removed is now covered by an error case that was there for parenthesized module expr, if someone is curious), and it works as intended.

Comment author: @mshinwell

@sliquister Please provide a Github PR with the patch, thanks.

Comment author: @garrigue

This is #949 (almost ready to merge).

Comment author: @garrigue

#949 merged at commit d8fc8dc.