Denis Erfurt

name collision will be solved soon in solidity by implementing a new in and output format. See the current draft: https://pad.riseup.net/p/7x3G896a3NLA (Contract names will now be prefixed by the path...

Also with [this](https://github.com/ethereum/solidity/blob/c06ba01136e9594648a2d362f2767b967f2d0c1f/docs/layout-of-source-files.rst#importing-other-source-files) name collision is solvable: ``` pragma solidity ^0.4.0; import {A as AA} from "./a1/a.sol"; import {A as AB} from "./a2/a.sol"; contract ASD is AA { bool val;...

> Rather than overloading the new keyword, I think importing libraries should overload importing constants, which is how we describe non-library singleton contracts. Consider the case: let Math be a...

> unless we put a linker into the interpreter contract =]]]] If i understand linker correctly, this is easy todo with a in memory function: ``` c Bytes.substitude(bytes memory source,...

Do we want to support multiple libraries with the same name during the development process? e.g. Math provided and included by two different packages with different functionality

you could think of the following scenario. package A and B provide different Libraries named `Math`. You have two contract files a.sol and b.sol. a.sol imports and links against A.Math...

After talking to @ryepdx we decided to put multiple names and complex linking of libraries on hold right now and pick this task up with the chain forking task as...

Hmmm, this is a tricky one. with mappings we would need to map to addresses and loose type safety which means we would need to adapt something like @dbrock suggested:...

@nmushegian: are other usages of dapple install in use? Currently ipfs/ git/ dapphub are supported. Github is restricted to provide an exact commit hash during installation. Currently I've just refactored...

Tim just recently released testrpc version 2.0 and also resolved the delegatecall issue. @ryepdx maybe worth another try? Also testrpc is node v0.12 compatible: how complex do you think would...