-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Anagram Issue with tests #22
Comments
Thanks for the info! This is one of those things where different compilers have different idiosyncracies. We have a namespace |
Soo can you fix this or what? It would literally take 1 minute. |
Hi @lennthevator - for small fixes we always leave the option open to the poster to fix it first, once we've determined that the fix is welcome. If you don't want to submit a patch, that's totally cool, we can do it. ❤️ |
I don't know how to submit a patch. |
Ok, no problem. |
Well I tried to submit a patch, but Travis says that |
Sample implementations are in BOOST_AUTO_TEST_CASE(no_matches)
{
auto subject = anagram::matcher("diaper");
auto matches = subject.matches({"hello", "world", "zombies", "pants"});
vector<string> expected;
BOOST_REQUIRE_EQUAL_COLLECTIONS(expected.begin(), expected.end(), matches.begin(), matches.end());
} |
Alright, so you can change that to |
I suspect you aren't using gcc 4.8, as the travis build was compiling these just fine with gcc 4.8. |
Please do update pull request #26 which you've already opened, though. Thanks! |
So are you saying I should change |
I figured it out. I wasn't using namspaces at all. |
When I try to compile my program (which has no other errors in it) I get the error
anagram_test.cpp:9:45: error: cannot call constructor 'anagram::anagram' directly [-fpermissive]
I think you could just say
auto subject = anagram("diaper");
for the offending line, and all others like it.
The text was updated successfully, but these errors were encountered: