Expose LLL IR

[ralexstokes]

The current compiler v0.0.4 doesn't expose the LLL IR as it's own target. An implication of this is that you can't author LLL and then generate bytecode in an easy manner.

It would be ideal to eventually expose the LLL as a separate module that the vyper frontend (and any other frontend) could consume.

[djrtwo]

Important for Casper contract to remove it's reliance upon the Serpent compiler.

ethereum/casper#69
ethereum/casper#73

[fubuloubu]

sighasher looks like something that might be of more general utility. is that true?

Perhaps we can implement some of these functions as vyper primitives, if that makes sense. Or the portions of them which might make sense as primitives which allows you to compose larger functions out of those new primitives.

What portion of those casper contracts cannot be implemented using Vyper?

[dani-corie]

I do think we absolutely need a dedicated LLL compiler. This should be a separate EIP, shouldn't it?

[jacqueswww]

@daniel-jozsef for the time being, I will create vyper-lll command here.

@fubuloubu @ralexstokes
I am thinking of going full parethesis for the files, having a json format will just be very nasty.
I will make to build in expression names of main and init.

[fubuloubu]

lisp away!

[ralexstokes]

yeah -- the LLL source should just be a bunch of nested parens :)