ponder-lab / Hybridize-Functions-Refactoring / #2731

84%

main: 84%

Build Type

push

github

Committed by web-flow

Commit Message

Name a generated decorator instead of resolving it globally. (#851)

`@prop.setter` names an attribute of a property object defined in the same module, not a module-level definition anywhere. Asking the indexer to resolve the bare attribute matches every `setter` in the workspace, so the lookup reported an ambiguity, the decorator was dropped from the reported names, and a full stack trace went to the log for a case that is entirely well understood.

Its declaring module is the containing one by construction, so it is named directly. The existing ambiguous-definition fixture already carries the pattern, so the pin goes there rather than into a new fixture.

This addresses one class of the ambiguity failures a corpus run produces, and not the largest: ordinary names matching many definitions across a workspace holding every subject are a separate, scoping problem.

Coverage Stats

5 of 5 new or added lines in 1 file covered. (100.0%)

3 existing lines in 1 file now uncovered.

3052 of 3652 relevant lines covered (83.57%)

0.84 hits per line