[phobos] Why is scoped offered by a function?

[SHOO]

Ok, I see.
IMHO the cause is not to be able to use default constructers for structs.
The usage of struct seems to have changed compared with old times.
Recently, structs are not only a set of simple data anymore, and rather 
a role as the class instance seems to be importance than it.
The support from language specifications feels insufficient for it.
Hmm...

However, for this matter, you can ignore it. It is a problem to be 
settled if you make a destructor that is more safe for non-initialized 
data or throw AssertionError when using non-initialized data in runtime.
It is a problem which is more convenient.

(2010/08/08 4:55), Andrei Alexandrescu wrote:
> It was only an experiment. If there are reasons to change that,
> absolutely. One good reason for offering scope() as a function is that
> it makes it difficult to create uninitialized scoped objects.
>
> Andrei
>
> On 08/07/2010 03:13 AM, SHOO wrote:
>> Why is std.typecons.scoped offered by only a function?
>>
>> I think that a struct is offered is better than only a function.
>> For example, this allows following code:
>> http://ideone.com/LMADW
>>
>> I read some related posts in the past. They want scope member variables.
>> I think scoped!(T) has potential to become one solution for it.
>> _______________________________________________
>> phobos mailing list
>> phobos at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/phobos