Bernardo António Borda d'Água
Bernardo António Borda d'Água
We shall wait. And I don't think I understood this: > Regarding the parameters: I think we stick with the current approach, because declarative actions have the current action spec...
Sorry if I misread the RFC but there is stuff I'm sceptical about. What happens when a slot doesn't have a unique child? Will all top level children get assigned...
> The code of `Sink` is very very simple, and this struct exists mainly to make it easier to get started with rodio. In other words, using a `Sink` is...
I can take a stab at implementing this if you point me in the general direction
Exactly. Could even allow an attribute to toggle that behavior
It is 99% cosmetic. And I have it working as is right now. I'd say it's is somewhat semantic too though. Because in the rest of the app, my lib...
My suggestion here would be to do handle it like `syn` does. Have an `Enum` with the possible variants and a correspondent `struct` for every one.
This may be my least favourite thing about `syn-rsx`. The API doesn't feel very rusty. I just end up unwraping a lot. And then back tracking and discovering where the...
> This actually doesn't work since `Node::name/value` are options. I still feel like the API could use some improvement, just not sure how. Open to suggestions. It would still work,...
Let me know if I can help. I agree with everything you said. And about the duplication part, I'm not that familiar with `syn-rsx`'s internals, but we can implement the...