Nikolai Mushegian

``` (Foo x) = (Bar 1) (Main) = (Foo 0) (Main) = (\ x . (Bar 1)) (Foo 0) // lambda ``` Are these compiled identically? How do these concepts...

I see this is covered in “improvements needed”, I think I could give a go at this so this issue could be for discussing the API.

So this original thing fails to compile, ``` Invalid left-hand side On rule: `(Reflect (x y)) = (Tag x)`. ``` This lets me compile run the program (it does not...

I understand that you can't, but what I am asking is whether maybe you can, like theoretically could a reflection feature be built in like this in the current HVM...

> Initially they had different syntaxes (constructors used `[]`), but we found it aesthetically unappealing, so we used uppercase to distinguish. I can see how this caused confusion, though. Honestly...

to be clear, I mean apply this overall approach to move chunks of NFT's, not necessarily expose them as ERC20. Sectors are identified by (start,end)

ABORT opcode didn't exist before byzantium. Leaving this issue open until we double-check that latest version won't drain your gas like this. See this for context/history: https://github.com/ethereum/eips/issues/140

This repository contains the on-chain contract code, I'm not too familiar with the rest and the issue should probably be split up. See: https://github.com/oasisdex

keep in mind there is no order matching so "last trade" gives you no info / is exploitable for many purposes

You can write the general case into a singleton contract anyone can use: ``` composeActions(code, data) { deploy(code).delegatecall(data) } ``` Now write your atomic sequence in solidity ``` dapp1.doThis(); dapp2.doThat();...