-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
database_tests.cpp:74:49: error: use of overloaded operator '==' is ambiguous #439
Comments
you are probably under an old version. please try current database tests are all passing:
|
Its during the build (a compilation error), not the execution tests, since the last commit ( on Oct 24, 2017 , 6d6f5dd) |
ok, hold on, trying. |
just finished compilation:
git log shows i am at mentioned commit:
|
Seems we don't build on the same platform, i m using clang on osx. |
got it. will you mind instead of remove the line to try:
or:
if that compiles for you we may change it. |
Yes the second is ok (the cast), the first is not. |
thank you very much for testing. sent pull(#440). 1 more of the core devs need to approve it before i can merge. |
closing as fix was merged. |
the fix is merged in the develop branch. for us the issue is fixed. the develop branch is merged to master at release time. a release just went out and we do not know when we will be sending a new one so you should use the develop branch until then. |
switch to the
|
no because i have already fix the bug.( as i said i my comment above ). |
@Arthur111 yes, the fix has been merged into I'll create a "minor-fix" tag for them, so people who need them can checkout the tag. For example, for docker scripts, it's better to use a tag but not the |
Pushed a new tag
|
bitshares-core/tests/tests/database_tests.cpp:74:49: error:
use of overloaded operator '==' is ambiguous (with operand types
'const fc::unsigned_int' and 'int')
FC_ASSERT( bitusd.bitasset_data_id->instance == 0 );
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
if i comment // FC_ASSERT( bitusd.bitasset_data_id->instance == 0 );
compile is ok.
The text was updated successfully, but these errors were encountered: