Scalac report a deprecation warning inconsistently between var and def

[exoego]

Scalac report a warning on @deprecated(...) var if its type contains deprecated type.

@deprecated("Non-standard", "0.1")
class StreatmEvent {}

class RTCPeerConnection {
  @deprecated("Non-standard", "0.1")
  var onaddstream: js.Function1[StreatmEvent, _] = js.native
}

However, inconsitently, scalac does not report a warning on @deprecated(...) def that uses deprecated type.

@deprecated("Non-standard", "0.1")
class StreatmEvent {}

class RTCPeerConnection {
  @deprecated("Non-standard", "0.1")
  def onaddstream: js.Function1[StreatmEvent , _] = js.native

  @deprecated("Non-standard", "0.1")
  def onaddstream_= (handler: js.Function1[StreatmEvent , _]): Unit = js.native
}

For me working on scala-js/scala-js-dom#367, no warnings on member already marked as @deprecated is preferrable.
But it may depends on use case.

cc: @sjrd scala-js/scala-js-dom#367 (comment)

[som-snytt]

The annotation isn't winding up on the field. (Same issue with val.)

I looked at how it's done and went blind. Annotations from trees have to be attached to symbols. Possibly they are rethinking the mechanism #10459 I ran out of morning coffee before I saw why getters and setters work but not the field sym.

[dwijnand]

Fixed with scala/scala#8122