TatriX

If we gonna have multiple `check_xxx` methods, then perhaps ```rust request .fetch() .await .and_then(Status::check) // fetch::Result -> fetch::Result .and_then(Headers::check_content_type(&["text/plain"])) // fetch::Result -> fetch::Result .and_then(|response| my_check_headers(response.headers())) // fetch::Result -> fetch::Result .unwrap()...

It's easier to learn and should be easier to compose. In fact, what I really want is to get rid of [manual dispatch](https://github.com/seed-rs/seed-rs-realworld/blob/83ceb727ab3780337aa1340bd1902c7f678b611a/src/lib.rs#L261) Though I haven't put enough thoughts in...

After writing tones of markup using old and new macros my subjective conclusions is that I really dislike uppercase and shortened macros. So I strongly prefer `class![]` over `C![]` and...

Here's a quick and dirty demo of how I would like typed css to look like: ```rust fn main() { let s = attr::style(&[ css::position(css::Position::Relative), css::flex_grow(1), css::width(css::Auto), css::width((0, css::Auto)), ]);...

```rust css::w(css::Auto), css::my(0), css::mx(css::Auto), ``` What is `w`, `my` and `mx `? I have a guess, but I would argue that we shouldn't invent alternative parlance for styles and stick...

My take on this would be to use names exactly like in css, so I can copy styles from devtools replacing `-` with `_` and not have additional cognitive load...

> I still can't remember what each value means in `margin` It's quite simple to understand and thus remember. - one value = all - two values = top-bottom/left-right -...

Where can I look at the full code examples?

Makes perfect sense to me. If I can reuse existing components easily, I can get results faster. This property is crucial for decision making in commercial projects.

I have no idea what am I talking about, but is it possible to use `Deref` and `DerefMut` instead of get/set?