From 781457ad4eccf423cbf00e0519625e089b683bfc Mon Sep 17 00:00:00 2001 From: Richard Brooksby Date: Mon, 11 Apr 2016 06:36:28 +0100 Subject: [PATCH] Noting potential optimisation of superclass. Copied from Perforce Change: 190886 ServerID: perforce.ravenbrook.com --- mps/code/protocol.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/mps/code/protocol.h b/mps/code/protocol.h index 350ce316552..be18ffdb5d6 100644 --- a/mps/code/protocol.h +++ b/mps/code/protocol.h @@ -194,6 +194,9 @@ extern void InstFinish(Inst inst); * TODO: Several experiments with statically generating some kind of * SUPERCLASS lookup have failed because the names of types, classes, * and the hierarchy are inconsistent. Revisit this later. + * + * FIXME: Most uses of SUPERCLASS compile to constant expressions, but + * not that the compiler can tell. */ #define SUPERCLASS(kind, ident) \