As mentioned in #11, name collision are a problem. Namespacing properties and functions from mixins fixes the problem but introduces a new complication in dealing with mixins which I'm not sure can be abstracted away. Suggestions?
We should modify Mixable to throw an Error on a naming collision, and close this issue with the PR. That will be enough for now, maybe a better solution will present itself in the future (ES6 Block Scoping?)
As mentioned in #11, name collision are a problem. Namespacing properties and functions from mixins fixes the problem but introduces a new complication in dealing with mixins which I'm not sure can be abstracted away. Suggestions?