I think I get what you mean, but I cannot imagine a single example where your proposed &lt;LHS&gt; keyword would be a good solution: IMHO, if I need a keyword to make the RHS understandable to the reader and the (much smarter) compiler, a macro or function is called for to encapsulate the RHS in a named and documented unit of code.