Move cancellable to the type system and implement multi-parenting #1

已關閉

dgriffen 想從 dgriffen/rust.eventbus:dev/dgriffen/type-cancel 合併 3 個提交至 master

拉取自: dgriffen/rust.eventbus:dev/dgriffen/type-cancel

合併到: SoniEx2:master

SoniEx2:master

SoniEx2:dev

對話內容 5 程式碼提交 3 檔案變動 3 +104 -58

dgriffen 已留言 2018-10-29 03:57:23 +01:00

第一次貢獻者

複製連結

The dyn_events test was changed to produce the output requested in your sample here: https://bpaste.net/show/73d5e4bc55b4

The dyn_events test was changed to produce the output requested in your sample here: <https://bpaste.net/show/73d5e4bc55b4>

dgriffen 已留言 2018-10-29 03:59:24 +01:00

作者

第一次貢獻者

複製連結

This is the output produced when run with cargo test -- --nocapture

Got event for inspection and manipulation: MyEventImpl { i: 3 }
Got event for inspection, manipulation, and cancellation: MyExtraEventImpl { i: 4 }
Got event for inspection and manipulation: MyExtraEventImpl { i: 4 }

This is the output produced when run with `cargo test -- --nocapture` ```text Got event for inspection and manipulation: MyEventImpl { i: 3 } Got event for inspection, manipulation, and cancellation: MyExtraEventImpl { i: 4 } Got event for inspection and manipulation: MyExtraEventImpl { i: 4 } ```

SoniEx2 已留言 2018-10-29 04:06:11 +01:00

所有者

複製連結

The output requested in my sample should be done as a separate test. And it should use asserts somehow.

This also doesn't respect the hook priorities correctly.

The output requested in my sample should be done as a separate test. And it should use asserts somehow. This also doesn't respect the hook priorities correctly.

dgriffen 已留言 2018-10-29 04:10:55 +01:00

作者

第一次貢獻者

複製連結

Hook priorities is quite a large problem with the way this system is implemented. Rust really doesn't have a good built-in system for dynamic typing and downcasting which will have to be done in order to respect hook priorities since we'll be mixing up handlers a lot.

Hook priorities is quite a large problem with the way this system is implemented. Rust really doesn't have a good built-in system for dynamic typing and downcasting which will have to be done in order to respect hook priorities since we'll be mixing up handlers a lot.

SoniEx2 已留言 2018-10-29 04:15:31 +01:00

所有者

複製連結

Some way to generate identifiers (for use in a large enum or somesuch) would work just as well, I think, altho I'm not quite sure how to do that.

Some way to generate identifiers (for use in a large enum or somesuch) would work just as well, I think, altho I'm not quite sure how to do that.

dgriffen 已留言 2018-10-29 04:21:59 +01:00

作者

第一次貢獻者

複製連結

Ah yes, having the macro generate an enum large enough for each type would probably work great. I'm not sure if Rust supports turning a ty into an ident though.

Ah yes, having the macro generate an enum large enough for each type would probably work great. I'm not sure if Rust supports turning a `ty` into an `ident` though.

SoniEx2 關閉了這個合併請求 2018-12-03 16:45:02 +01:00

合併請求已關閉

請重新開放此合併請求以進行合併作業。

登入 才能加入這對話。

審核者

沒有審核者

標籤

清除已選取標籤

沒有項目

未選擇標籤

里程碑

清除已選取里程碑

沒有項目

沒有里程碑

專案

清除已選取專案

沒有項目

未選擇專案

負責人

清除負責人

沒有負責人

2 位參與者

通知

訂閱

截止日期

截止日期無效或超出範圍，請使用「yyyy-mm-dd」的格式。

未設定截止日期。

先決條件

未設定先決條件。

參考: SoniEx2/rust.eventbus#1

沒有提供敘述。