KORE milestone 1

**please review**

 - unit-tested convertors from KORE to KIL and back
 - significant changes and simplifications to KORE data structures. They are smaller and more powerful now

Is there a reason you're not calling the unparser? the KIL toString is not
necessarily guranteed to be sound with respect to uniqueness. Two different
terms can have the same toString.

On Mon, Dec 1, 2014 at 1:37 PM, Cosmin Radoi <notifications@github.com>
wrote:

> In
> k-distribution/src/test/resources/convertor-tests/syntaxWithAttributes-kilexpected.k:
>
> > @@ -0,0 +1,8 @@
> > +// Copyright (c) 2014 K Team. All Rights Reserved.
> > +
> > +DEF: null -> null
> > +module TEST
> > +  syntax Foo ::=
>
> Again, this is what KIL's toString() outputs.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kframework/k/pull/1211/files#r21113519>.
>