On Friday, 2 September 2016 at 10:29:41 UTC, David Nadlinger
wrote:
On Friday, 2 September 2016 at 08:57:14 UTC, Basile B. wrote:
On Friday, 2 September 2016 at 08:15:53 UTC, ketmar wrote:
std.traits wrappers should use __traits to build *safe*
things (declaring that @trusted in the end).
On Friday, 2 September 2016 at 08:14:33 UTC, Rory McGuire wrote:
Can we rather just make a special tagged union that is
scanned... rather avoid trying to make something that should be
minimal more and more complex? The compiler already treats some
parts of phobos as "special" as far as I
On Fri, 02 Sep 2016 09:40:56 +, ketmar wrote:
> On Friday, 2 September 2016 at 08:57:14 UTC, Basile B. wrote:
>> On Friday, 2 September 2016 at 08:15:53 UTC, ketmar wrote:
>>> std.traits wrappers should use __traits to build *safe* things
>>> (declaring that @trusted in the end).
>>
>> This
On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan wrote:
Through the work I did and the research of a couple of GC
topics, I discovered that I really enjoyed working on the
garbage collector and I plan on continuing that. I was recently
accepted to the University of Washington's
On Friday, 2 September 2016 at 08:57:14 UTC, Basile B. wrote:
On Friday, 2 September 2016 at 08:15:53 UTC, ketmar wrote:
std.traits wrappers should use __traits to build *safe* things
(declaring that @trusted in the end).
This has nothing to do with memory safety.
Actually it does, albeit
On Fri, Sep 2, 2016 at 10:15 AM, ketmar via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> On Friday, 2 September 2016 at 07:46:30 UTC, Rory McGuire wrote:
> actually, from my PoV solution is supereasy: just remove ALL visibility
> restrictions for traits. and i mean all.
On Friday, 2 September 2016 at 08:57:14 UTC, Basile B. wrote:
On Friday, 2 September 2016 at 08:15:53 UTC, ketmar wrote:
std.traits wrappers should use __traits to build *safe* things
(declaring that @trusted in the end).
This has nothing to do with memory safety.
i wonder who told you that
On Friday, 2 September 2016 at 08:15:53 UTC, ketmar wrote:
std.traits wrappers should use __traits to build *safe* things
(declaring that @trusted in the end).
This has nothing to do with memory safety. It's just that
protection attributes were invented for OOP and when applied to
template
On Friday, 2 September 2016 at 07:46:30 UTC, Rory McGuire wrote:
actually, from my PoV solution is supereasy: just remove ALL
visibility restrictions for traits. and i mean all. allMembers
should return all members, getMember should allow to access *any*
existing member without annoying
On Fri, Sep 2, 2016 at 9:46 AM, Jeremy DeHaan via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> [snip]. Precisely scanning unions is tricky since they could mix pointer
> and non pointer types. [snip]
>
Can we rather just make a special tagged union that is scanned...
On Friday, 2 September 2016 at 06:54:57 UTC, Ali Çehreli wrote:
On 09/01/2016 08:25 PM, Jeremy DeHaan wrote:
> I will still continue working on it in the hopes it'll get in.
Great news! :)
> I
> discovered that I really enjoyed working on the garbage
collector
If that's not motivation
On Friday, 2 September 2016 at 05:19:57 UTC, thedeemon wrote:
On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan
wrote:
Hi everyone,
I know I'm super late to the party for this, and sorry for
that. While my work on the precise GC didn't go as planned, it
is closer than it was to be
On Fri, Sep 2, 2016 at 8:47 AM, ketmar via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> On Friday, 2 September 2016 at 06:27:11 UTC, Rory McGuire wrote:
>
>> Perhaps @system code should just completely ignore privacy?
>>
>
> it is uncontrollable. imagine attribute
On 09/01/2016 08:25 PM, Jeremy DeHaan wrote:
> I will still continue working on it in the hopes it'll get in.
Great news! :)
> I
> discovered that I really enjoyed working on the garbage collector
If that's not motivation enough...
> I was recently accepted to the University of Washington's
On Friday, 2 September 2016 at 06:27:11 UTC, Rory McGuire wrote:
Perhaps @system code should just completely ignore privacy?
it is uncontrollable. imagine attribute inference: today, your
function was inferred @system, and it sees everything. and
tomorrow you fixed some other things, and now
On 02 Sep 2016 07:40, "ketmar via Digitalmars-d-announce" <
digitalmars-d-announce@puremagic.com> wrote:
>
> On Tuesday, 30 August 2016 at 23:54:45 UTC, Martin Nowak wrote:
>>
>> Allowing access to private members has a lot of implications, e.g.
breaks lots of optimizations b/c you can't know who
16 matches
Mail list logo
