Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: new gopool pkg #38

Merged
merged 1 commit into from
Jan 8, 2025
Merged

feat: new gopool pkg #38

merged 1 commit into from
Jan 8, 2025

Conversation

xiaost
Copy link
Collaborator

@xiaost xiaost commented Jan 2, 2025

What type of PR is this?

feat

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

license-eye has totally checked 53 files.

Valid Invalid Ignored Fixed
51 2 0 0
Click to see the invalid file list
  • concurrency/gopool/gopool.go
  • concurrency/gopool/gopool_test.go

concurrency/gopool/gopool.go Show resolved Hide resolved
concurrency/gopool/gopool_test.go Show resolved Hide resolved
@xiaost xiaost force-pushed the feat/gopool branch 3 times, most recently from 332a546 to 0996143 Compare January 2, 2025 06:30
@xiaost xiaost changed the title feat: now gopool pkg feat: new gopool pkg Jan 2, 2025
AsterDY
AsterDY previously approved these changes Jan 3, 2025
@AsterDY AsterDY merged commit 52ba607 into main Jan 8, 2025
27 checks passed
@AsterDY AsterDY deleted the feat/gopool branch January 8, 2025 10:15
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants