Improve flexibility of message sending API

[jstarry]

The message sending api for ComponentLink<_> could be more flexible and user-friendly if it accepted Into<Msg> instead of Msg.

pub fn batch_callback<F, IN>(&self, function: F) -> Callback<IN>
where
    F: Fn(IN) -> Vec<COMP::Message> + 'static;

pub fn callback<F, IN>(&self, function: F) -> Callback<IN>
where
    F: Fn(IN) -> COMP::Message + 'static;

pub fn send_message(&mut self, msg: COMP::Message);

pub fn send_message_batch(&mut self, msgs: Vec<COMP::Message>);

More flexibility with Into<COMP::Message>

pub fn batch_callback<F, IN>(&self, function: F) -> Callback<IN>
where
    F: Fn(IN) -> Vec<Into<COMP::Message>> + 'static;

pub fn callback<F, IN>(&self, function: F) -> Callback<IN>
where
    F: Fn(IN) -> Into<COMP::Message> + 'static;

pub fn send_message(&mut self, msg: Into<COMP::Message>);

pub fn send_message_batch(&mut self, msgs: Vec<Into<COMP::Message>>);

[Manish-Giri]

@jstarry Hello, may I take this up? Another contributor has already submitted a few issues corresponding to the todos, before I could assemble all of them, so maybe I can help out here instead.

[jstarry]

@Manish-Giri yes, sounds great. Appreciate the help :)

[jstarry]

Hey @Manish-Giri, how's it going? Have you had time to look into this yet? I'm happy to help if you have any questions!

[captain-yossarian]

@jstarry if @Manish-Giri does not mind, I will pick it up

[jstarry]

@captain-yossarian go for it

[lukerandall]

@jstarry I believe this is resolved by #999

[jstarry]

Ah yup, thanks!