lemunozm/termchat

update to latest version of message-io

Closed this issue · 4 comments

I would like to use termchat with the latest version of message-io, but there are some incompatibilities. Is it much work to align them?

Cargo build gives the following errors when using message-io v0.14.3

error[E0432]: unresolved import `message_io::events::EventQueue`
  --> src/application.rs:18:26
   |
18 | use message_io::events::{EventQueue};
   |                          ^^^^^^^^^^ no `EventQueue` in `events`

error[E0432]: unresolved import `message_io::network::Network`
  --> src/application.rs:19:37
   |
19 | use message_io::network::{NetEvent, Network, Endpoint, Transport};
   |                                     ^^^^^^^ no `Network` in `network`

error[E0432]: unresolved import `message_io::network::Network`
 --> src/action.rs:3:27
  |
3 | use message_io::network::{Network};
  |                           ^^^^^^^ no `Network` in `network`

error[E0432]: unresolved import `message_io::network::Network`
 --> src/commands/send_file.rs:7:27
  |
7 | use message_io::network::{Network};
  |                           ^^^^^^^ no `Network` in `network`

error[E0107]: this enum takes 0 generic arguments but 1 generic argument was supplied
  --> src/application.rs:24:13
   |
24 |     Network(NetEvent<NetMessage>),
   |             ^^^^^^^^ ---------- help: remove this generic argument
   |             |
   |             expected 0 generic arguments
   |
note: enum defined here, with 0 generic parameters
  --> /home/jbos/Data/src/capitar-io/message-io/src/network/driver.rs:19:10
   |
19 | pub enum NetEvent<'a> {
   |          ^^^^^^^^

error[E0106]: missing lifetime specifier
  --> src/application.rs:24:22
   |
24 |     Network(NetEvent<NetMessage>),
   |                      ^ expected named lifetime parameter
   |
help: consider introducing a named lifetime parameter
   |
23 ~ pub enum Event<'a> {
24 ~     Network(NetEvent<'a, NetMessage>),
   |

Hi @janjaapbos,

The API to the last version changed in some parts and is not straightforward.

I did not update because currently, it's working without network issues, but it could be a good idea to leave it working with the latest. I will try to update it in the next few days.

That would be great. Thank you!

message-io updated to the latest version in #50 already merged. The v1.3.1 uses this version. Some features could not be compatible with a termchat of previous versions as v1.3.0.

Thank you very much!