From b1f3af70685985974fafaeb8f3df991d158d2a01 Mon Sep 17 00:00:00 2001 From: Michael Williamson Date: Wed, 6 Jan 2016 22:16:16 +0000 Subject: Remove completed TODO --- README.md | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 81ccf1f..15a9d89 100644 --- a/README.md +++ b/README.md @@ -4,18 +4,6 @@ * Boxing and unboxing for `String`s -* Method overloads, probably by renaming (since some languages don't support - overloading, and relying on other languages overloading semantics is risky). - Having a consistent way of naming methods would be nice, - but using the fully-qualified names of arguments/return types would be - rather long. Referencing those by an integer ID is an alternative, - albeit less readable (and prone to change). Perhaps a reference by - just the simple name of the class, with an integer ID if the codebase - has more than one type of the same name? - - Overloading is done for the interpreter. Partially done for the Python - backend: currently only supports overloading by number of arguments. - * Handle boxing/unboxing when overriding method in supertype with more/less specific return types/arguments. For instance, if an interface defines a method that returns `Object`, then a subtype may override that method -- cgit v1.2.3