realm/SwiftLint

`generic_type_name` triggers incorrectly for integer generic parameters

Open

#6,213 opened on Aug 30, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Swift (19,570 stars) (2,295 forks)batch import
enhancementgood first issue

Description

Bug Description

SE-0452 introduced integer generic parameters, which are placed alongside other generic parameters, but, in contrast to "normal" (type) generic parameters, are spelled like variables, ie starting with a lowercase identifier. SwiftLint current;y doesn

// This triggers a violation:
struct Foo<let count: Int> {}

Mention the command or other SwiftLint integration method that caused the issue. Include stack traces or command output.

$ swiftlint

Environment

  • SwiftLint version: 0.59.1 (Homebrew)
  • Xcode version: Xcode 26.0 (17A5305f)
  • Configuration file: default configurations

Contributor guide

Tech stack
swift
Domain
toolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Swift genericsSwiftLint rule structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the `GenericTypeNameRule` implementation in SwiftLint's source code (likely under `Source/SwiftLintFramework/Rules/`). Understand how the rule currently identifies generic type names and why integer generic parameters (introduced in SE 0452) are incorrectly triggering. Look at the existing test cases for that rule and add a new test case for `struct Foo<let count: Int> {}`. The fix likely involves updating the rule's logic to exclude integer generic parameters from the name check.