0.1.3 checklist
=============

- check jar CLI
org.mirah:mirah doesn't work w/o JRuby currently
org.mirah:mirah-complete jar is also broken in 0.1.2, 0.1.1
:/
otoh, probably no one is using them since they don't work

- check jruby gem
0.1.2 is the broken :(

- done: silence run compiler logging
- done: make sure in run mode we don't drop things on the filesystem
- silence logging by default in RunCommand, w/ options overriding it.


- Java 8
-- make asm new d/l dependency
-- find usages of org.jruby...asm & change them
-- rm jruby-complete asa d/l dep
-- add asm license file to dist bundle

- mirah-parser CI (ish)
- automated tests for distribution artifacts
- CI passing


------------------





- Check mvn compile plugin
- move build artifacts to javalib for gem

- verify bytecode version of compiler
- silence logging from JRuby interfaces, unless overridden.

Misc
===========
- mirah-parser maven artifact

- java 9
- implicit void methods w/ explicit return generate incorrect bytecode. Let's see if that's true of explicit. nope.
- get rid of all outputs that escape from tests
- default toString?

etc
=========

- Reflection Macros
- AST formatter that converts back to something the parser can parse

- switch to minitest

from notes, uncategorized
============================
#fuzzy aka cast scoping
for rescue clauses
eg
e = nil
begin
rescue X => e
  # e is "X" here
rescue Y => e
  # e is "Y" here
end
puts e # e is LUB(X, Y)

#behavior literate, exec spec
list o example code + what the compiler says when you give it to the compiler
things like errors, & behavior

feature requests
----------------
- goto: headius wants it
- synchronize intrinsic ala java's
- file scoped macros
- move macro / mirahc anno to separate class dir to improve javac interop

parser
-------

foo {|a| !a || ''.equals(a) }
doesn't parse

does now :)


blocks don't introduce new scopes when they are part of a macro currently :/


Release management
------------------

keep version in fewer places
whew