"Exceptions will fade away in modern languages"

[Ola Fosheim Grostad]

On Thursday, 26 November 2020 at 00:23:01 UTC, Meta wrote:
> On Wednesday, 25 November 2020 at 23:23:17 UTC, Araq wrote:
>> On Wednesday, 25 November 2020 at 17:15:14 UTC, Meta wrote:
>>> I think Nim actually does have exceptions.
>>
>> Correct and the one of the "deterministic" kind (check after 
>> function calls that can raise). It doesn't require 
>> "inter-procedural dataflow anlysis" either but hey, what do I 
>> know, have fun in your nonscientific bubble.
>
> I don't understand the hostility. What did I say that was 
> "unscientific"? For that matter, I didn't say anything about 
> interprocedural analysis.

He is the Nim author. :)

But, @live tries to do things that is better done through the 
type system and RAII.
To make RAII work you need exceptions. Removing them would be a 
disaster. What is wrong with make_unique?

The time complexity to do it without type system constraints will 
most likely make @live underwhelming or slow down compilation 
significantly.

Why encourage using malloc directly in the first place?

To get @safe ARC, D needs a global borrow checker to prevent 
dangling interior pointers. Without it, D will be stuck with a 
heavyhanded GC for all @safe code.