Skip to content
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

remove concurrent base/stringvalue, use boost::barrier instead #3848

Merged
merged 11 commits into from
Feb 10, 2022
Merged

remove concurrent base/stringvalue, use boost::barrier instead #3848

merged 11 commits into from
Feb 10, 2022

Conversation

jiayuehua
Copy link
Contributor

@jiayuehua jiayuehua commented Jan 29, 2022

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

How do you solve it?

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

  • Unit test(positive and negative cases)
  • Function test
  • Performance test
  • N/A

Affects:

  • Documentation affected (Please add the label if documentation needs to be modified.)
  • Incompatibility (If it breaks the compatibility, please describe it and add the label.)
  • If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
  • Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

@@ -1,115 +0,0 @@
#! /usr/bin/env bash
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why delete this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

now use system gcc or user install itselt

Copy link
Contributor

@Shylock-Hg Shylock-Hg Jan 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This script won't prevent user try gcc him want. And this script is used by our infra now, plz check it first instead of delete directly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better not to delete the script until we've finished the discussion about compiler usage.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok.

@jiayuehua jiayuehua added the ready-for-testing PR: ready for the CI test label Feb 8, 2022
@darionyaphet
Copy link
Contributor

it seems replace the concurrent with boost thread library? if so please update the title. thanks ~

@jiayuehua jiayuehua changed the title remove concurrent stringvalue remove concurrent base/stringvalue, use boost::barrier instead Feb 9, 2022
zhaohaifei
zhaohaifei previously approved these changes Feb 10, 2022
Copy link
Contributor

@zhaohaifei zhaohaifei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

look good to me

@@ -1,115 +0,0 @@
#! /usr/bin/env bash
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better not to delete the script until we've finished the discussion about compiler usage.

NonCopyable(const NonCopyable&) = delete;
NonCopyable& operator=(const NonCopyable&) = delete;
};
class NonMovable {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there no nonmovable implementation in boost ?

Copy link
Contributor Author

@jiayuehua jiayuehua Feb 10, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no I search boost and folly codebase ,find nonthing.

@@ -5,7 +5,7 @@

set(OPTIMIZER_TEST_LIB
$<TARGET_OBJECTS:base_obj>
$<TARGET_OBJECTS:concurrent_obj>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cleanup

@@ -42,7 +42,7 @@ nebula_add_test(
$<TARGET_OBJECTS:time_obj>
$<TARGET_OBJECTS:fs_obj>
$<TARGET_OBJECTS:base_obj>
$<TARGET_OBJECTS:concurrent_obj>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

* @brief A wrapper class of batchs of log, support put/remove/removeRange
*/
class BatchHolder : public nebula::cpp::NonCopyable, public nebula::cpp::NonMovable {
class BatchHolder : public boost::noncopyable, public nebula::cpp::NonMovable {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that the comment of this class should not be deleted.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

has reverted

liwenhui-soul pushed a commit to liwenhui-soul/nebula that referenced this pull request Feb 15, 2022
…t-inc#3848)

* remove concurrent stringvalue

* delete cmakesetting.json

* clang format code

* revert format arg...

* objectpool format

* boost thread linkage

* revert install-gcc.sh
@jiayuehua
Copy link
Contributor Author

#3774

yixinglu pushed a commit to yixinglu/nebula that referenced this pull request Mar 21, 2022
…t-inc#3848) (vesoft-inc#605)

* remove concurrent stringvalue

* delete cmakesetting.json

* clang format code

* revert format arg...

* objectpool format

* boost thread linkage

* revert install-gcc.sh

Co-authored-by: yuehua.jia <3423893+jiayuehua@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants