“Convert to computed property” should not be offered when function does not have a return value

[ahoppen]

When I have the following, we shouldn’t offer the Convert to computed property refactoring action because the function returns Void / has no return value and thus a computed property does not make sense.

struct Foo {
  func test() {
  }
}

[DPrakashhh]

I have submitted a Pull Request (#2433) to address this. The fix includes logic to handle implicit "Void", explicit Void, and empty tuples "()", along with regression tests for each scenario.

I have an exam tomorrow, but I'll be available shortly after to address any feedback or changes you might have