chriseth

We could also add the information about the functions.

discussion: linkreferences and immutables should be in the same structure as "information about a section of the bytecode"

Main open question: - should it be nested? - what are the use-cases?

It turns out that the situation is not different for errors. Since nobody is using natspec, I tend to increment the version counter for the next release and collect some...

What is the actual goal here? `-t` is used to specify test unit names. It would be nice if also files could be tested directly, but do we really want...

I think we should support calling `isoltest` directly on single files - regardless of where `isoltest` is called from, i.e. `isoltest bla.sol` (without `-t`). Maybe we can split this into...

This is true because the supplied library addresses are considered compiler input. After all, the compiler actually inserts the addresses into its output. This is related to the metadata hash...

This looks to me like a limitation of etherscan - it should allow both ways to link the binary.

The compiler does not warn because ``MemoryInterface::getUint`` is external. It is impossible to refer to it just via `getUint`, you always need a contract type for it.

Ah sorry about that! You can can maybe get around this by moving the function into its own file and importing the file as a module.