EndilWayfare

This is a fantastic addition! I was about to submit a pull request of my own that just forwarded the `watchOptions` on the `compiler` itself, if set, because they weren't...

You can, of course, explicitly spell it out in the meantime ```rust pub fn cause_bstr_to_happen() -> winapi::shared::wtypes::BSTR { let bstr: BStr = "Hello World".into(); let ptr = bstr.as_ptr(); std::mem::forget(bstr); ptr...

I was looking into this crate for Yew styling as well, and I noticed the same issue. Any time `Style::create` is called, a new `` element is unconditionally created and...

The concrete `Style` instance is never used by client code for anything other than its `class_name` string. Maybe instead of `Style::create` returning a full `Style` instance (as a "constructor with...

Or maybe return some kind of `StyleHandle` with a `Drop` implementation that communicates with the registry? Up to this point, I was thinking solely in terms of avoiding duplicate inserts....

I'm saying "public method" here, because I assume that the current design continues to hide the global `STYLE_REGISTRY` behind public methods on the `Style` type. This is nice, because frameworks...

I don't mean to bust in and leave a pile of "here's some demands for some seriously complicated API changes ok bye!" I'm interested in helping out with implementation, if...

Hey, @lukidoescode! Yeah, there's never enough hours in the day, I hear ya. I've never published an open-source crate; all my work is proprietary, internal company software. As far as...

Just glancing over it, that looks like a promising start! I may draft a PR of my own, whoever gets around to it first, I guess :) Some thoughts: -...

I think it's wise to keep code as similar as possible between platforms, deviating only where absolutely necessary or where there are significant "wins" (performance or otherwise). This should make...