From c776477ce018f10e21a7130599a016d231296484 Mon Sep 17 00:00:00 2001
From: Andreas Rumpf <rumpf_a@web.de>
Date: Tue, 3 Apr 2018 16:05:20 +0200
Subject: [PATCH] Updated Destructors (rest)

---
 Destructors.rest | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Destructors.rest b/Destructors.rest
index 9878161..9994820 100644
--- a/Destructors.rest
+++ b/Destructors.rest
@@ -160,6 +160,14 @@ An analysis like "every code path provable leads to the parameters consumption"
 
 **Solution**: The analysis can introduce a fallback path with hidden bool flags like ``if not flag: =destroy(sinkParam)``. Furthermore the compiler should probably get even smarter in its inference of ``raises: []``.
 
+This solution has been implemented.
+
+
+Object and array constructors
+=============================
+
+Passing a value ``x`` to an object or array constructor as in ``MyObject(field: x)`` is conceptually the same as ``=sink(myobj.field, x)``. This still needs to be implemented.
+
 
 Interactions with the GC
 ========================