Overriding fields to be final

Consider this code:
```dart
class A {
bool _temp;
bool get temp => _temp;
set temp(bool value) {
print("Changing A.temp to $value");
_temp = value;
}

A(this._temp);
}

class B extends A {
@override
final bool temp;

B(this.temp) : super(temp);
}

void main() {
final A a = A(true);
a.temp = false; // "Changing A.temp to false"
print(a.temp); // false

final B b = B(true);
b.temp = false; // "Changing A.temp to false"
print(b.temp); // true
}
```

Based on the print statements, it seems that Dart is referring to A's setter because B doesn't have one. I can confirm this because when I changed B.temp from final to a getter and setter like A has, B's print statements ran instead. But this behavior is unintuitive, and I would expect this to either error or B's getter to return whatever A's setter received.

Start with the Dart example in the issue and reproduce the interaction between B's final field and A's setter. Review the language rules governing overridden fields, getters, and setters, then determine which of the two proposed behaviors—an error or a getter reflecting the setter's value—is intended as the completed outcome.

Written by the indexing model from the issue text.