[Development] QUIP 6: removing top-level const from return types

Thiago Macieira thiago.macieira at intel.com
Tue May 23 16:17:46 CEST 2017

On Monday, 22 May 2017 22:26:38 PDT Marc Mutz wrote:
> > if there's a chance of existing code breaking
> How can removing top-level const from a return type "break" existing code
> any more than adding a function overload?

I thought we were discussing Source Incompatible Changes. If it doesn't break 
anything, it isn't SIC.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list