Mojo: Report bindings validation errors via MojoNotifyBadMessage

mojo/public/cpp/bindings/lib/connector.h

Index: mojo/public/cpp/bindings/lib/connector.h
diff --git a/mojo/public/cpp/bindings/lib/connector.h b/mojo/public/cpp/bindings/lib/connector.h
index 243159ef32fdbe0417824bd0a50431a39903f96a..d3db95f1a725d1a31e9b838a1c7d55ba4aa0870d 100644
--- a/mojo/public/cpp/bindings/lib/connector.h
+++ b/mojo/public/cpp/bindings/lib/connector.h
@@ -99,7 +99,7 @@ class Connector : public MessageReceiver {
   // an error because it believes the other end is malicious). In order to
   // appear to the user that the connector still binds to a message pipe, it
   // creates a new message pipe, closes one end and binds to the other.
-  void RaiseError();
+  void RaiseError(Result error);
 
   // Is the connector bound to a MessagePipe handle?
   bool is_valid() const {
@@ -117,7 +117,7 @@ class Connector : public MessageReceiver {
   void ResumeIncomingMethodCallProcessing();
 
   // MessageReceiver implementation:
-  bool Accept(Message* message) override;
+  Result Accept(Message* message) override;
 
   MessagePipeHandle handle() const {
     DCHECK(thread_checker_.CalledOnValidThread());