From 12d4bee3187d97483d2c2c37610722da278e90ed Mon Sep 17 00:00:00 2001 From: joeduffy Date: Wed, 25 Jan 2017 17:16:17 -0800 Subject: [PATCH] Add todos referencing marapongo/mu#56 --- pkg/compiler/eval/eval.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pkg/compiler/eval/eval.go b/pkg/compiler/eval/eval.go index 167f632a4..3dc30e35d 100644 --- a/pkg/compiler/eval/eval.go +++ b/pkg/compiler/eval/eval.go @@ -524,7 +524,7 @@ func (e *evaluator) evalLoadLocationExpression(node *ast.LoadLocationExpression) case *symbols.ClassMethod: // Create a new readonly ref slot, pointing to the method, that will abandon if overwritten. contract.Assert(this != nil) - // TODO: should we be more "dynamic" and permit overwriting of methods? I suspect yes, for compat. + // TODO[marapongo/mu#56]: consider permitting "dynamic" method overwriting. pv = &Reference{ obj: NewFunctionObject(s, this), readonly: true, @@ -543,7 +543,7 @@ func (e *evaluator) evalLoadLocationExpression(node *ast.LoadLocationExpression) case *symbols.ModuleMethod: // Create a new readonly ref slot, pointing to the method, that will abandon if overwritten. contract.Assert(this == nil) - // TODO: should we be more "dynamic" and permit overwriting of methods? I suspect yes, for compat. + // TODO[marapongo/mu#56]: consider permitting "dynamic" method overwriting. pv = &Reference{ obj: NewFunctionObject(s, nil), readonly: true,