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

Add a guide to creating a separate module for benchmarks #175

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

qurbonzoda
Copy link
Collaborator

Followup to #170

The changes were developed within GSoC 2023 program by our mentee @wldeh.

docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
docs/separate-benchmark-module.md Outdated Show resolved Hide resolved
@qurbonzoda qurbonzoda requested a review from ilya-g January 4, 2024 13:04
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@Goooler Goooler left a comment

Choose a reason for hiding this comment

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

And the title should be Add a guide for creating instead of to?

docs/separate-benchmark-source-set.md Outdated Show resolved Hide resolved
3. **Register Benchmark Source Set**

Register your benchmark source set. This informs the kotlinx-benchmark tool
that benchmarks reside within this source set and need to be executed accordingly.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
that benchmarks reside within this source set and need to be executed accordingly.
about benchmarks reside within this source set and need to be executed accordingly.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I am not sure if the change is grammatically correct.

@qurbonzoda
Copy link
Collaborator Author

qurbonzoda commented Jan 25, 2024

And the title should be Add a guide for creating instead of to?

I surfed the internet, and it seems both prepositions are fine to use in this case.

… docs/separate-benchmark-module.md

Co-authored-by: Filipp Zhinkin <filipp.zhinkin@gmail.com>
Co-authored-by: Zongle Wang <wangzongler@gmail.com>
@qurbonzoda qurbonzoda changed the base branch from add-tasks-overview-guide to master February 8, 2024 23:43
@qurbonzoda qurbonzoda merged commit f5a7f25 into master Feb 8, 2024
@qurbonzoda qurbonzoda deleted the add-separate-benchmark-module branch February 11, 2024 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants