You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing a component with twice the same event fails at compile time.
It causes a conflict in the generation of the Msg, as it currently uses a hash of the event's code token tree.
There is no easy resolution for this as the Msg event id must be deterministic.
We could hash the children's code with it, but that would invalidate any loop-generated component.
Another idea would be to have an incremental id in the macro's scope that would serve as a salt, but this is not easy either due to the multi-dimensional nature of the self-expanding html_macro!{}
This fails at compile time:
component!{i32,
div {
div @click: { *self += 1}{}
div @click: { *self += 1}{}}}
The text was updated successfully, but these errors were encountered:
Writing a component with twice the same event fails at compile time.
It causes a conflict in the generation of the Msg, as it currently uses a hash of the event's code token tree.
There is no easy resolution for this as the Msg event id must be deterministic.
We could hash the children's code with it, but that would invalidate any loop-generated component.
Another idea would be to have an incremental id in the macro's scope that would serve as a salt, but this is not easy either due to the multi-dimensional nature of the self-expanding html_macro!{}
This fails at compile time:
The text was updated successfully, but these errors were encountered: