Backlog gardening

I pushed some mid-term realistic options to GitHub issues tagged `backlog`.

See https://github.com/golo-lang/golo-lang/issues?labels=backlog&page=1&state=open

backlog.markdown

@@ -8,23 +8,8 @@ Not everything is deemed to be implemented...
 
 * Annotations.
 
-* Allow underscores in number literals.
-
-* Ability to define classes and / or data objects.
-  Must be lightweight, and complex use-cases should be done in POJOs.
-
-* Common collection literals.
-
-* String templates, e.g. `"Hello #{foo} #{Bar.baz()}!"` or `"Current time: #{System.currentTime()}"`.
-
-* Elvis
-
 ## Runtime
 
-* Java Array wrapper?
-
-* Common collection sugar functions (lists, maps, sets, ...)
-
 * Cache method / function resolution in the runtime support classes.
 
 * Investigate adaptive handling of types.
@@ -38,14 +23,3 @@ Not everything is deemed to be implemented...
 * Concurrent compilation?
 
 * Look if thread locals could not be judiciously used in some places.
-
-## Tooling
-
-* Ensure that the generated bytecode helps in the Java debugger.
-
-* Maven: get incremental compilation. Tests?
-
-* Ant, Gradle plugins.
-
-* golodoc.
-