Skip to content

Fix GitHub Actions build warnings, Marker style should be * #1925

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

Merged
merged 1 commit into from
Jun 15, 2022

Conversation

N-Dekker
Copy link
Contributor

Addressed:

16132:1-16132:75 warning Marker style should be * unordered-list-marker-style
16133:1-16133:39 warning Marker style should be * unordered-list-marker-style
16134:1-16134:57 warning Marker style should be * unordered-list-marker-style
16135:1-16135:62 warning Marker style should be * unordered-list-marker-style
16136:1-16136:240 warning Marker style should be * unordered-list-marker-style
16137:1-16137:194 warning Marker style should be * unordered-list-marker-style
16141:1-16141:72 warning Marker style should be * unordered-list-marker-style
16142:1-16142:49 warning Marker style should be * unordered-list-marker-style

Addressed:
> 16132:1-16132:75   warning  Marker style should be `*`  unordered-list-marker-style
> 16133:1-16133:39   warning  Marker style should be `*`  unordered-list-marker-style
> 16134:1-16134:57   warning  Marker style should be `*`  unordered-list-marker-style
> 16135:1-16135:62   warning  Marker style should be `*`  unordered-list-marker-style
> 16136:1-16136:240  warning  Marker style should be `*`  unordered-list-marker-style
> 16137:1-16137:194  warning  Marker style should be `*`  unordered-list-marker-style
> 16141:1-16141:72   warning  Marker style should be `*`  unordered-list-marker-style
> 16142:1-16142:49   warning  Marker style should be `*`  unordered-list-marker-style
@cubbimew cubbimew merged commit 81dfb48 into isocpp:master Jun 15, 2022
bgloyer added a commit to bgloyer/CppCoreGuidelines that referenced this pull request Jun 16, 2022
* F.16 ("in" parameters): Move Matrix example to F.20 (return values) (isocpp#1922)

The `Matrix` example and the notes about assignment appear off-topic in rule F.16, as F.16 is specifically about "in" parameters.

With help from Sergey Zubkov.

* SL.io.50 (Avoid `endl`): Mention string streams (isocpp#1920)

Explicitly mentioned string streams as `endl` insertions into string streams do actually occur in the wild.

With help from Sergey Zubkov.

* Extended E.16 to include copy ctor for exception type, closes isocpp#1921

* Fix GitHub Actions build warnings, Marker style should be `*` (isocpp#1925)

* restored reference

* Added references to note

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>
bgloyer added a commit to bgloyer/CppCoreGuidelines that referenced this pull request Jul 9, 2022
* F.16 ("in" parameters): Move Matrix example to F.20 (return values) (isocpp#1922)

The `Matrix` example and the notes about assignment appear off-topic in rule F.16, as F.16 is specifically about "in" parameters.

With help from Sergey Zubkov.

* SL.io.50 (Avoid `endl`): Mention string streams (isocpp#1920)

Explicitly mentioned string streams as `endl` insertions into string streams do actually occur in the wild.

With help from Sergey Zubkov.

* Extended E.16 to include copy ctor for exception type, closes isocpp#1921

* Fix GitHub Actions build warnings, Marker style should be `*` (isocpp#1925)

* C.166: Use markdown format and document title for link (isocpp#1929)

* C.9: Improve an inline link (isocpp#1933)

Avoid ending the sentence with a dangling "see".

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>
Co-authored-by: Francisco Moretti <[email protected]>
Co-authored-by: Sven van Haastregt <[email protected]>
bgloyer added a commit to bgloyer/CppCoreGuidelines that referenced this pull request Jul 9, 2022
* Update CppCoreGuidelines.md

* Update CppCoreGuidelines.md

* Update isocpp.dic

* use snake casing

* sake case naming

* C 32 comments (#3)

* F.16 ("in" parameters): Move Matrix example to F.20 (return values) (isocpp#1922)

The `Matrix` example and the notes about assignment appear off-topic in rule F.16, as F.16 is specifically about "in" parameters.

With help from Sergey Zubkov.

* SL.io.50 (Avoid `endl`): Mention string streams (isocpp#1920)

Explicitly mentioned string streams as `endl` insertions into string streams do actually occur in the wild.

With help from Sergey Zubkov.

* Extended E.16 to include copy ctor for exception type, closes isocpp#1921

* Fix GitHub Actions build warnings, Marker style should be `*` (isocpp#1925)

* restored reference

* Added references to note

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>
bgloyer added a commit to bgloyer/CppCoreGuidelines that referenced this pull request Jul 9, 2022
* F.16 ("in" parameters): Move Matrix example to F.20 (return values) (isocpp#1922)

The `Matrix` example and the notes about assignment appear off-topic in rule F.16, as F.16 is specifically about "in" parameters.

With help from Sergey Zubkov.

* SL.io.50 (Avoid `endl`): Mention string streams (isocpp#1920)

Explicitly mentioned string streams as `endl` insertions into string streams do actually occur in the wild.

With help from Sergey Zubkov.

* Extended E.16 to include copy ctor for exception type, closes isocpp#1921

* Fix GitHub Actions build warnings, Marker style should be `*` (isocpp#1925)

* C.166: Use markdown format and document title for link (isocpp#1929)

* C.9: Improve an inline link (isocpp#1933)

Avoid ending the sentence with a dangling "see".

* C 32 (#5)

* Update CppCoreGuidelines.md

* Update CppCoreGuidelines.md

* Update isocpp.dic

* use snake casing

* sake case naming

* C 32 comments (#3)

* F.16 ("in" parameters): Move Matrix example to F.20 (return values) (isocpp#1922)

The `Matrix` example and the notes about assignment appear off-topic in rule F.16, as F.16 is specifically about "in" parameters.

With help from Sergey Zubkov.

* SL.io.50 (Avoid `endl`): Mention string streams (isocpp#1920)

Explicitly mentioned string streams as `endl` insertions into string streams do actually occur in the wild.

With help from Sergey Zubkov.

* Extended E.16 to include copy ctor for exception type, closes isocpp#1921

* Fix GitHub Actions build warnings, Marker style should be `*` (isocpp#1925)

* restored reference

* Added references to note

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>
Co-authored-by: Francisco Moretti <[email protected]>
Co-authored-by: Sven van Haastregt <[email protected]>
hsutter added a commit that referenced this pull request Jul 13, 2022
* Update CppCoreGuidelines.md

* Update CppCoreGuidelines.md

* Update isocpp.dic

* use snake casing

* sake case naming

* C 32 comments (#3)

* F.16 ("in" parameters): Move Matrix example to F.20 (return values) (#1922)

The `Matrix` example and the notes about assignment appear off-topic in rule F.16, as F.16 is specifically about "in" parameters.

With help from Sergey Zubkov.

* SL.io.50 (Avoid `endl`): Mention string streams (#1920)

Explicitly mentioned string streams as `endl` insertions into string streams do actually occur in the wild.

With help from Sergey Zubkov.

* Extended E.16 to include copy ctor for exception type, closes #1921

* Fix GitHub Actions build warnings, Marker style should be `*` (#1925)

* restored reference

* Added references to note

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>

Co-authored-by: Niels Dekker <[email protected]>
Co-authored-by: Herb Sutter <[email protected]>
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.

2 participants