Skip to content

changelog: fix grammar and naming in pending entries - #23530

Open
dkorpel wants to merge 1 commit into
dlang:masterfrom
dkorpel:changelog-fixes
Open

changelog: fix grammar and naming in pending entries#23530
dkorpel wants to merge 1 commit into
dlang:masterfrom
dkorpel:changelog-fixes

Conversation

@dkorpel

@dkorpel dkorpel commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Reviewed by Claude for the 2.113 beta

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dkorpel dkorpel added the Review:Trivial typos, formatting, comments label Aug 5, 2026

@thewilsonator thewilsonator left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

otherwise looks good

Comment thread changelog/dmd.fastdfa.dd
Comment on lines +4 to +6
The intent of the engine is to be both fast and free from false positives; if successful, it may in the future be turned on by default.

No attributes have been implemented to date, before they are considered the engine itself must be both usable with the right tradeoffs and have desirable features.
This has some side effects, it prevent separate compilation, function pointers, and cyclic functions from being analysable.
No attributes have been implemented to date; before they are considered, the engine itself must be both usable with the right tradeoffs and have desirable features.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

what's with the semi colons? The first one should be full stop, the second one should be a comma.

Only in a mathematical expression.

This was not originally part of the fast DFA engines scope, its continued existence depends upon community feedback as part of usage.
This was not originally part of the fast DFA engine's scope; its continued existence depends upon community feedback as part of usage.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

semi-colon should be a full stop

PetarKirov added a commit to PetarKirov/sparkles that referenced this pull request Aug 7, 2026
Where a reviewer reads them: under the anchor line, not in a margin and not in
a separate pane where the code they refer to has scrolled away (the Gerrit
`gr-diff` shape). A thread on the old side hangs on the removed line its
author actually saw, never on the new one.

A resolved thread folds to one line. Not tidiness: an unresolved conversation
is a thing the reviewer must ACT on, and rendering a settled argument at the
same weight buries the live one. The badge still says who and how many - the
demote-never-hide contract `DVN2` already holds for noise.

`AnchoredThread` is forge-neutral and lives with the session, so `DCM2`'s
local comments will produce exactly the same value: no forge type reaches the
renderer, and a locally-authored thread is not a second kind of thing. That is
what "the thread block is one widget" has to mean to be worth saying.

Comment bodies are markdown, rendered through hue's own view - the one place
it would be strange for markdown not to be markdown.

Verified live on dlang/dmd#23530 (this repository has no PR with review
threads to test against). The live run also corrected the indentation
mechanism: a prefix span only ever lands on the FIRST row of a wrapped body,
leaving the rest hanging at the code's own column where it reads as code.
Padding indents every row.

Claude-Session: https://claude.ai/code/session_01YQJw7nA1exWvgh7w5tEZsu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Review:Trivial typos, formatting, comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants