There is a discussion about introducing "descriptive" diagnostics of the same style happening on the Swift Forums at the moment - https://forums.swift.org/t/pitch-extended-error-messages-dia....
I this it's a great idea and with new diagnostic architecture described in the blog post it would be relatively easy to archive.
This is the diagnostic produced for similar example using new diagnostic architecture:
error: binary operator '+' cannot be applied to operands of type 'String' and 'Int'
_ = "a" + 1
~~~ ^ ~
note: overloads for '+' exist with these partially matching parameter lists: (Int, Int), (String, String)_ = "a" + 1
^
note: candidate expects value of type 'String' for parameter #2 @inlinable public static func + (lhs: String, rhs: String) -> String
^
note: candidate expects value of type 'Int' for parameter #1 public static func + (lhs: Int, rhs: Int) -> Int
^
I am reminded of a recent tweet: "We spent decades trying to invent a sufficiently smart compiler when we should have been inventing a sufficiently empathetic one"[2]
Edit: if you have to Google to understand what the compiler is saying, I consider that a bug. File tickets for confusing diagnostics!
[1]: https://play.rust-lang.org/?version=nightly&mode=debug&editi...
[2]: https://twitter.com/mostlysafe/status/1176170363266449410