From 8e4e55e2573be990077bb82aa89332e92ace8751 Mon Sep 17 00:00:00 2001 From: "Felix S. Klock II" Date: Wed, 5 Aug 2015 20:38:26 +0200 Subject: [PATCH] fill in a final missing step in the reasoning presented. --- text/0000-nonparametric-dropck.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/text/0000-nonparametric-dropck.md b/text/0000-nonparametric-dropck.md index e250565ef65..aab682378ba 100644 --- a/text/0000-nonparametric-dropck.md +++ b/text/0000-nonparametric-dropck.md @@ -465,7 +465,8 @@ All `fn drop` methods would be required to be `#[unspecialized]`. It is the second bullet that makes this an ad-hoc effect system: it provides a recursive property ensuring that during the extent of the call to `foo`, -we will never invoke a function marked as `default`. +we will never invoke a function marked as `default` (and therefore, I *think*, +will never even potentially invoke a method that has been specialized). It is also this second bullet that represents a signficant burden on the destructor implementor. In particular, it immediately rules out