sync/atomic: amend comments for Value.{Swap,CompareAndSwap}

[austinderek]

Related to CL 241661, CL 403094.

---

🔄 This is a mirror of upstream PR golang#76259

[staging]

HackerOne Code Security Review

🟢 Scan Complete: 2 Issue(s)
🟠 Validation Complete: One or more Issues looked potentially actionable, so this was escalated to our network of engineers for manual review. Once this is complete you'll see an update posted.

Here's how the code changes were interpreted and info about the tools used for scanning.

📖 Summary of Changes

The modification involves a minor documentation update in the CompareAndSwap method comment within the atomic value implementation. The change subtly adjusts the grammatical phrasing of the type inconsistency description, potentially improving clarity for developers reading the method's documentation.

File	Summary
src/sync/atomic/value.go	Minor documentation change in CompareAndSwap method comment, adjusting the description of type inconsistency handling from "CompareAndSwap of an inconsistent type" to "CompareAndSwap of inconsistent types".

ℹ️ Issues Detected

NOTE: These may not require action!

Below are unvalidated results from the Analysis Tools that ran during the latest scan for transparency. We investigate each of these for accuracy and relevance before surfacing them as a potential problem.

How will I know if something is a problem?
When validation completes, any concerns that warrant attention prior to merge will be posted as inline comments. These will show up in 2 ways:

• Expert review (most cases): Issues will be posted by experts who manually reviewed and validated them. These are real HackerOne engineers (not bots) reviewing through an integrated IDE-like tool. You can communicate with them like any other reviewer. They'll stay assigned and get notified with commit & comment updates.
• Automatically: In cases where our validation checks have highest confidence the problem is legitimate and urgent. These will include a description of contextual reasoning why & actionable next steps.

File & Line	Issue
src/sync/atomic/value.go Line 154	Use of unsafe calls should be audited
src/sync/atomic/value.go Line 103	Use of unsafe calls should be audited

🧰 Analysis tools

• [ ✅ ] HackerOne AI Code Analysis
• [ ✅ ] HackerOne AI Code Validation
• [ ✅ ] semgrep
• [ ✅ ] gosec
• [ ✅ ] bandit

⏱️ Latest scan covered changes up to commit 7fbb715 (latest)