Redundant error for missing type annotation in computed property

Description

func foo() {
  var int {}
}

error: computed property must have an explicit type [computed_property_missing_type]
  91 | 
  92 | func foo() {
  93 |   var int {}
     |       `- error: computed property must have an explicit type [computed_property_missing_type]
  94 | }
  95 | 

error: type annotation missing in pattern [cannot_infer_type_for_pattern]
  91 | 
  92 | func foo() {
  93 |   var int {}
     |       `- error: type annotation missing in pattern [cannot_infer_type_for_pattern]
  94 | }
  95 | 

Contributor guide

Tech stack

swift

Domain

developer experiencetooling

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.

blocked

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

understanding of Swift compiler diagnostics

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

Investigate the type checker or diagnostic emission module in the Swift compiler to locate where the two errors ('computed property missing type' and 'cannot infer type for pattern') are emitted. The goal is to suppress the second error when the first is already emitted. Review existing patterns in the codebase for suppressing duplicate diagnostics. Check the issue comments for any additional context or guidance from maintainers.