Skip to content

docs: fix grammar on style-guide #678

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.

Sign up for GitHub

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

Open
abelaba wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −3
Open

docs: fix grammar on style-guide #678

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/source/development/styleguide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,9 +49,9 @@ Your contribution should fulfill the criteria provided below.
on the selected benchmark sets and other things. In such situations, dictionaries that
map strings to BenchmarkProblem objects are a good idea.

- Think about autocomplete! If want to accept a string as argument (e.g. an algorithm
name) also accept input types that are more amenable to static analysis and offer
better autocomplete.
- Think about autocomplete! If you want to accept a string as an argument (e.g. an
algorithm name) also accept input types that are more amenable to static analysis and
offer better autocomplete.

- Whenever possible, use immutable types. Whenever things need to be changeable,
consider using an immutable type with copy constructors for modified instances.
Expand Down
Loading