• Spacen Jasset (5/5) Nov 19 2015 I thought scope was deprecated, but I see that this is still
• Jeremy DeHaan (5/10) Nov 19 2015 Using scope to allocate on the stack is what you are thinking of,
• Alex Parrill (10/15) Nov 20 2015 The usage of scope as a variable storage modifier to allocate

Spacen Jasset <spacen razemail.com> writes:

I thought scope was deprecated, but I see that this is still 
here: http://dlang.org/attribute.html#scope

Is it just the uses on classes and local variables that are 
discouraged, but the use in a function signature will continue? 
in == const scope?

Jeremy DeHaan <dehaan.jeremiah gmail.com> writes:

On Thursday, 19 November 2015 at 23:16:04 UTC, Spacen Jasset 
wrote:
 I thought scope was deprecated, but I see that this is still 
 here: http://dlang.org/attribute.html#scope

 Is it just the uses on classes and local variables that are 
 discouraged, but the use in a function signature will continue? 
 in == const scope?

Using scope to allocate on the stack is what you are thinking of, 
but it was only marked for deprecation.

http://dlang.org/deprecate.html#scope%20for%20allocating%20classes%20on%20the%20stack

Alex Parrill <initrd.gz gmail.com> writes:

On Thursday, 19 November 2015 at 23:16:04 UTC, Spacen Jasset 
wrote:
 I thought scope was deprecated, but I see that this is still 
 here: http://dlang.org/attribute.html#scope

 Is it just the uses on classes and local variables that are 
 discouraged, but the use in a function signature will continue? 
 in == const scope?

The usage of scope as a variable storage modifier to allocate 
classes on the stack is deprecated, and replaced with 
std.typecons.scoped.

The usage of scope as a parameter attribute is not deprecated, 
and is used to indicate that references to the parameter will not 
escape through this function call (ex. the function won't store 
the parameter in a global variable), though the only thing it 
affects at the moment is delegates.