Skip to content

Correct confusing headers in HLSLDocs #100017

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 3 commits into from
Jul 23, 2024
Merged

Correct confusing headers in HLSLDocs #100017

merged 3 commits into from
Jul 23, 2024

Conversation

pow2clk
Copy link
Contributor

@pow2clk pow2clk commented Jul 22, 2024

AvailabilityDiagnostics.rst and ExpectedDifferences.rst both had multiple headers that were perceived to be the "top-level".

In AvailabilityDiagnostics.rst two headers had both over and underlines. The second was the "Examples" section so it showed up in the top level HLSL docs. The overline is removed here so it's clear it's a subheader.

In ExpectedDifferences.rst, the first header had no overline, so a few headers that looked the same were included. The overline is added to the top header to make clear that it's the main header.

Because AvailabilityDiagnostics.rst mistakenly overlined the "Examples"
section, it was included in the generated HLSLDocs page.
By demoting it to a subheader, it shouldn't show up as a top-level
HLSLDocs page.
@pow2clk pow2clk added clang Clang issues not falling into any other category HLSL HLSL Language Support labels Jul 22, 2024
Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be
notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write
permissions for the repository. In which case you can instead tag reviewers by
name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review
by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate
is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot
Copy link
Member

llvmbot commented Jul 22, 2024

@llvm/pr-subscribers-hlsl

@llvm/pr-subscribers-clang

Author: Greg Roth (pow2clk)

Changes

Because AvailabilityDiagnostics.rst mistakenly overlined the "Examples" section, it was included in the generated HLSLDocs page. By demoting it to a subheader, it shouldn't show up as a top-level HLSLDocs page.


Full diff: https://github.com/llvm/llvm-project/pull/100017.diff

1 Files Affected:

  • (modified) clang/docs/HLSL/AvailabilityDiagnostics.rst (-1)
diff --git a/clang/docs/HLSL/AvailabilityDiagnostics.rst b/clang/docs/HLSL/AvailabilityDiagnostics.rst
index bb9d02f21dde6..7ce82c1946b87 100644
--- a/clang/docs/HLSL/AvailabilityDiagnostics.rst
+++ b/clang/docs/HLSL/AvailabilityDiagnostics.rst
@@ -52,7 +52,6 @@ If the compilation target is a shader library, only availability based on shader
 
 As a result, availability based on specific shader stage will only be diagnosed in code that is reachable from a shader entry point or library export function. It also means that function bodies might be scanned multiple time. When that happens, care should be taken not to produce duplicated diagnostics.
 
-========
 Examples
 ========
 

@pow2clk
Copy link
Contributor Author

pow2clk commented Jul 22, 2024

See https://clang.llvm.org/docs/HLSL/HLSLDocs.html to see the effect

ExpectedDifference sections were bleeding into the top page too
@pow2clk pow2clk changed the title Correct confusing header in HLSLDocs Correct confusing headers in HLSLDocs Jul 22, 2024
Justin pointed out that the earlier change moved the examples out
from the examples section. By demoting them as well, they will stay put
@bogner bogner merged commit ad6685b into llvm:main Jul 23, 2024
6 of 7 checks passed
Copy link

@pow2clk Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested
by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as
the builds can include changes from many authors. It is not uncommon for your
change to be included in a build that fails due to someone else's changes, or
infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself.
This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

@pow2clk pow2clk deleted the hlsldocsfix branch July 23, 2024 02:19
@hekota
Copy link
Member

hekota commented Jul 24, 2024

Thanks @pow2clk !

yuxuanchen1997 pushed a commit that referenced this pull request Jul 25, 2024
AvailabilityDiagnostics.rst and ExpectedDifferences.rst both had
multiple headers that were perceived to be the "top-level".

In AvailabilityDiagnostics.rst two headers had both over and underlines.
The second was the "Examples" section so it showed up in the top level
HLSL docs. The overline is removed here so it's clear it's a subheader.

In ExpectedDifferences.rst, the first header had no overline, so a few
headers that looked the same were included. The overline is added to the
top header to make clear that it's the main header.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang Clang issues not falling into any other category HLSL HLSL Language Support
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants