DIP1000: Scoped Pointers (Discussion)
Yuxuan Shui via Digitalmars-d
digitalmars-d at puremagic.com
Thu Aug 11 15:15:07 PDT 2016
On Thursday, 11 August 2016 at 21:28:57 UTC, sclytrack wrote:
> On Wednesday, 10 August 2016 at 20:36:38 UTC, Dicebot wrote:
>> http://forum.dlang.org/post/pqsiqmkxenrwxoruzaml@forum.dlang.org
>>
>> The first DIP has just landed into the new queue. It is a
>> proposal from language authors and thus it bypasses usual
>> nitpicking process and proceeds straight to requesting
>> community (your!) feedback.
>>
>> Essentially, it is an attempt to solve reference lifetime
>> problem by extending implementation of `scope` keyword.
>>
>> Proposal text:
>> https://github.com/dlang/DIPs/blob/master/DIPs/DIP1000.md
>>
>> Few notes:
>>
>> - Please submit pull requests to adjust the markdown document
>> if you want to propose any improvements (mentioning
>> @WalterBright and @andralex for confirmation).
>> - The proposal refers to a number of other documents and it is
>> recommended to become familiar at least briefly with all of
>> them.
>> - At this point the question I'd personally suggest to be
>> evaluated is "does this proposal enable enough useful
>> designs?". A good check would be to try taking some of your
>> projects and see if having DIP1000 approved and implemented
>> could improve them.
>
>
> There is confusion between what lifetime and visibility in the
> DIP.
> (Well, I am confused)
>
I'm a confused by the terminology as well.
lifetime(p) denotes the lifetime of the value which is referred
to by 'p', is that correct? And visibility(p) denotes the
lifetime of 'p' itself?
I found this very confusing...
More information about the Digitalmars-d
mailing list