Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove boost dependency #349
Conversation
Codecov Report
@@ Coverage Diff @@
## master #349 +/- ##
==========================================
- Coverage 79.77% 79.73% -0.04%
==========================================
Files 110 110
Lines 8565 8565
==========================================
- Hits 6832 6829 -3
- Misses 1733 1736 +3
|
| @@ -57,7 +57,6 @@ ExperimentalAutoDetectBinPacking: false | |||
| FixNamespaceComments: false | |||
| ForEachMacros: | |||
| - Q_FOREACH | |||
achamayou
Sep 3, 2019
Member
Do we use Q_FOREACH? That looks like a Qt thing. I assume we can get rid of it too?
eddyashton
Sep 3, 2019
Author
Contributor
Ah, nope. Turns out that removing this messes with formatting of our foreach functions:
static int foreach (lua_State* l)
UD::unbox(l, -2)->foreach ([l, ifunc](const K& k, const V& v)
These are methods where we want without a space (rather than the for () space). It seems that having any value here is sufficient, but I think it's best to leave a useful value (Q_FOREACH) rather than random junk?
eddyashton
Sep 3, 2019
•
Author
Contributor
Have gone with FOREACH rather than suggesting Qt support.
* Remove boost from ansible * Remove unused boost references * Add dockerignore, remove clang-format Q_FOREACH * Restore Q_FOREACH * Non-specific FOREACH macro




CCF doesn't depend on Boost - remove it from ansible playbooks, and references elsewhere.