From 73a9d9cfd8de837f80fe96dfd457986212965fa3 Mon Sep 17 00:00:00 2001 From: Tony Garnock-Jones Date: Tue, 20 Nov 2018 13:22:44 +0000 Subject: [PATCH] Note in HOWITWORKS about `opaque-placeholder`. --- imperative/HOWITWORKS.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/imperative/HOWITWORKS.md b/imperative/HOWITWORKS.md index 3caec1f..b74f0cb 100644 --- a/imperative/HOWITWORKS.md +++ b/imperative/HOWITWORKS.md @@ -543,6 +543,10 @@ interested in the `present` constructor. trigger its "matching" inner endpoint, but not the inner endpoint of the other endpoint, even though you might expect the relayed assertion to do so. + - There's also a need for `(opaque-placeholder)`s to frustrate + constant-matching against literal `(discard)` in cases of + visibility restriction. See commit b4f1d36 and test case + `test/core/nesting-confusion-2.rkt`. - there's more to say about the implementation of the *dataspace* itself, not just the index structures. For example, the care that