set() set_external(), =operator() overloads, etc are ambiguous on Windows (Visual Studio)

[cyrush]

From Kathleen B.:
Wow, I have this in my test :
proc0["cycle"] = 120;
worked fine on linux, but Visual studio complains that it is ambiguous:
15> error C2593: 'operator =' is ambiguous
15> Node.h(923): could be 'conduit::Node &conduit::Node::operator =(conduit::float64)'
15> Node.h(922): or 'conduit::Node &conduit::Node::operator =(conduit::float32)'
15> Node.h(920): or 'conduit::Node &conduit::Node::operator =(conduit::uint64)'
15> Node.h(919): or 'conduit::Node &conduit::Node::operator =(conduit::uint32)'
15> Node.h(918): or 'conduit::Node &conduit::Node::operator =(conduit::uint16)'
15> Node.h(917): or 'conduit::Node &conduit::Node::operator =(conduit::uint8)'
15> Node.h(915): or 'conduit::Node &conduit::Node::operator =(conduit::int64)'
15> Node.h(914): or 'conduit::Node &conduit::Node::operator =(conduit::int32)'
15> Node.h(913): or 'conduit::Node &conduit::Node::operator =(conduit::int16)'
15> Node.h(912): or 'conduit::Node &conduit::Node::operator =(conduit::int8)'
15> d): or 'conduit::Node &conduit::Node::operator =(conduit::bool8)'
15> while trying to match the argument list '(conduit::Node, int)'

[cyrush]

From Kathleen:
We aren't the only ones with this puzzle:
http://stackoverflow.com/questions/21971278/ambiguous-call-of-long-unsigned-int-for-uint32-t
Form Cyrus:
We have a case where to types are actually the same underlying type. Some how we are able to generate both set methods, but when it comes time to use them the compiler can't figure out how to select which one.

[cyrush]

I am working on resolving this in a sandboxed repo here:
https://github.com/cyrush/msvsover

I have this repo setup to build w/ co on windows (appveyor) and osx + linux (travis)

[cyrush]

resolved in PR #63