On Tuesday, 20 April 2021 at 01:12:22 UTC, Walter Bright wrote:
> I'll be doing a reprise of my DConf 2020 talk on Destroy All Memory Corruption on April 21, 2021 at 7PM PST.
>
> https://nwcpp.org/
>
> Except this time it'll be live, not prerecorded.
>
> All are welcome!

Nice, good presentation. I actually learned some things!

What is the current state of @live?
Any edge cases to be aware of?

Thanks

On Tuesday, 20 April 2021 at 01:12:22 UTC, Walter Bright wrote:
> I'll be doing a reprise of my DConf 2020 talk on Destroy All Memory Corruption on April 21, 2021 at 7PM PST.
>
> https://nwcpp.org/
>
> Except this time it'll be live, not prerecorded.
>
> All are welcome!

One remark I found interesting regarding reference counting.

"In order to properly run the destructor, you have to run the destructor in an exception handler"

Why do you need to run the destructor in an exception handler?

On Saturday, 24 April 2021 at 18:16:51 UTC, IGotD- wrote:
> One remark I found interesting regarding reference counting.
>
> "In order to properly run the destructor, you have to run the destructor in an exception handler"
>
> Why do you need to run the destructor in an exception handler?

I assume it's to ensure that objects are destroyed properly when unwinding the stack. Might be possible to avoid in `nothrow` code.

On 4/24/2021 2:53 PM, Paul Backus wrote:
> I assume it's to ensure that objects are destroyed properly when unwinding the stack. Might be possible to avoid in `nothrow` code.

Yes, you can avoid this in nothrow code.

On Friday, 23 April 2021 at 09:06:20 UTC, Walter Bright wrote:
> On 4/21/2021 6:31 PM, Ali Çehreli wrote:
>> This is happening in half an hour. It requires MS Teams, which requires a MS (or Skype) account.
>
> I was a bit concerned about this, so a couple days earlier Lloyd and I worked to get everything configured and working at my end.
>
> It worked smoothly, but one thing I didn't like was I couldn't see anyone else on my screen. It was kinda hard to talk to my slides, trying to imagine the audience. Perhaps I had it set up wrong.

No, you had it right. It's the inherent limitation of MS Teams!