Repository navigation
docs: record the rule behind generator target names - #48
Merged
Merged
Conversation
owenthcarey
force-pushed
the
docs/target-naming-rationale
branch
from
September 17, 2026 03:55
1611876 to
b08d116
Compare
owenthcarey
marked this pull request as ready for review
September 17, 2026 03:56
Add a Target names section to the naming reference that states how a generator's target is named (after the language when the output is idiomatic to one language, after the runtime when several languages consume it equally, never after a deployment platform), and records why dotnet and kotlin are both applications of that rule, including why the android target became kotlin in schema 0.9.0.
owenthcarey
force-pushed
the
docs/target-naming-rationale
branch
from
September 17, 2026 04:06
b08d116 to
40eaa11
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #47, which renamed the
androidtarget tokotlin.Adds a Target names subsection to
docs/src/reference/naming.mdso the reasoning behind target names is written down once instead of being rediscovered whenever a generator is added or thedotnetvskotlinasymmetry is noticed. It states the rule:swift,python,kotlin, ...);dotnet,node,wasm);[generators.<target>].It then records why
dotnet(notcsharp) andkotlin(notandroidorjvm) both follow from that rule, and gives new generators a test to apply.Verification:
scripts/check-links.shpasses locally against v0.23.0main. Docs-only change; no code touched.