I'd call it a bug in the sense that this error message is totally unhelpful for solving the 'real' underlying issue which seems like it could have been arbitrarily distant from the error location. I've definitely experienced this more with SwiftUI where the compiler gets confused typechecking the monster expressions that view body properties end up containing.
5 Likes