On Friday, 2 September 2016 at 14:55:26 UTC, jmh530 wrote:

> Anyway, with @safe unions, my thinking is that it would mean that the garbage collector can be made precise in @safe code in a way that it can't in @system code (assuming unions with pointers aren't snuck in through @trusted).

GC (and runtime in general) has no idea what code is safe and what code is system. GC works with data at run-time. All @safe-related stuff is about code (not data!) and happens at compile-time. They are completely orthogonal and independent, as I understand.

On Saturday, 3 September 2016 at 12:22:25 UTC, thedeemon wrote:
>
> GC (and runtime in general) has no idea what code is safe and what code is system. GC works with data at run-time. All @safe-related stuff is about code (not data!) and happens at compile-time. They are completely orthogonal and independent, as I understand.

I don't see why you wouldn't be able to use compile-time information like __traits with the runtime.

In my head, I imagine that at compile-time you can figure out which unions are in @safe functions, add a UDA to each (so you're marking data, not code), and then read that information at run-time (like with __traits).

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 getting merged.
>
> [...]

In Mac 32 bit. the test is not pass.

On Tuesday, 6 September 2016 at 14:56:15 UTC, jmh530 wrote:

>> GC (and runtime in general) has no idea what code is safe and what code is system. GC works with data at run-time. All @safe-related stuff is about code (not data!) and happens at compile-time. They are completely orthogonal and independent, as I understand.
>
> I don't see why you wouldn't be able to use compile-time information like __traits with the runtime.
>
> In my head, I imagine that at compile-time you can figure out which unions are in @safe functions, add a UDA to each (so you're marking data, not code), and then read that information at run-time (like with __traits).

UDAs are also purely compile-time, they don't exist as run-time data.

On Saturday, 3 September 2016 at 12:22:25 UTC, thedeemon wrote:
> On Friday, 2 September 2016 at 14:55:26 UTC, jmh530 wrote:
>> Anyway, with @safe unions, my thinking is that it would mean that the garbage collector can be made precise in @safe code in a way that it can't in @system code (assuming unions with pointers aren't snuck in through @trusted).
>
> GC (and runtime in general) has no idea what code is safe and what code is system. GC works with data at run-time. All @safe-related stuff is about code (not data!) and happens at compile-time. They are completely orthogonal and independent, as I understand.

This is correct, but when designing a GC – in particular, a precise GC –, having the compiler emit additional helpful metadata to binaries is always an option worth considering.

 — David

On Wednesday, 7 September 2016 at 02:15:30 UTC, Dsby 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 getting merged.
>>
>> [...]
>
> In Mac 32 bit. the test is not pass.

I didn't have a mac to test this on at the time. I currently have some things ordered so that I can see what is actually going on and fix this.

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 getting merged.
>
> [...]

On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan wrote:
Hi,how about the precise GC, now?

On Friday, 14 October 2016 at 03:26:31 UTC, FrankLike 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 getting merged.
>>
>> [...]
>
> On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan wrote:
> Hi,how about the precise GC, now?

I want to known too.

On Monday, 17 October 2016 at 02:59:15 UTC, Dsby wrote:
> On Friday, 14 October 2016 at 03:26:31 UTC, FrankLike 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 getting merged.
>>>
>>> [...]
>>
>> On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan wrote:
>> Hi,how about the precise GC, now?
>
> I want to known too.

I was asked the same question on github, but I'll answer it here too with a couple more details.

I've done a little work, but not enough to getit finished. I started school a couple of weeks ago and I'm still trying to get my schedule figured out, but I'm hoping to start putting some regular effort into it starting next week.

On Sunday, 23 October 2016 at 05:34:08 UTC, Jeremy DeHaan wrote:
> On Monday, 17 October 2016 at 02:59:15 UTC, Dsby wrote:
>> On Friday, 14 October 2016 at 03:26:31 UTC, FrankLike 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 getting merged.
>>>>
>>>> [...]
>>>
>>> On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan wrote:
>>> Hi,how about the precise GC, now?
>>
>> I want to known too.
>
> I was asked the same question on github, but I'll answer it here too with a couple more details.
>
> I've done a little work, but not enough to getit finished. I started school a couple of weeks ago and I'm still trying to get my schedule figured out, but I'm hoping to start putting some regular effort into it starting next week.

Did anything happen?