Okay, I figured it out. Abstractly this is actually a really clever refactor of the thing that was happening before, but it's *such a bad API* wow. Designing good APIs is a lot of trial & error. Also what constitutes a "good API" changes as the language evolves.
-
-
Show this thread
-
In this case: I just found out how to add trait bounds, and how to implement conversions. Coupled with a carrier type with an arbitrary body it's become a thing that's super hard to understand lol. Clever for sure, but ooph this is terrible to use.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.