On 9/4/15 8:20 AM, Steven Schveighoffer wrote:
On 9/1/15 3:13 PM, Jacob Carlborg wrote:
On 2015-09-01 15:40, Steven Schveighoffer wrote:

I'm not 100% sure, but that does seem like a bug.

I see now that there's a deprecation message when compiling with
2.067.0. So it looks like it's intended.


Really? I don't see any deprecation message for your exact code posted
when compiled on 2.067.

I take it back, the message occurs if you make the function concrete.

-Steve

Reply via email to