panicbit

I decided to switch to `hyper` to get rid of the dependency on `curl`, though, it turns out to probably not be worth it. A lot of the Request/Url caching...

I'm not using Windows primarily but AFAIK setting up native dependencies is a pain.

I'm not saying that you shouldn't, but I guess it would be nice to gradually move towards pure Rust crates. Hyper sadly still has a dependency on `openssl`.

We are apparently already doing that, but we're not linking there in the readme https://panicbit.github.io/fcm-rust/fcm/index.html . We should probably add a link to that **and** to docs.rs.

This might be solved together with #1 **IF** we go the abstract_platform way. See for example [the ctypes](https://github.com/panicbit/abstract_platform/blob/e60d2959563152e4438ac1e6a6257ca155cf66c8/traits.rs#L25-L37) or [memchr](https://github.com/panicbit/abstract_platform/blob/e60d2959563152e4438ac1e6a6257ca155cf66c8/traits.rs#L94-L95). Platform implementations can depend on whatever they want/need. It might...

> [Experimentation by @panicbit](https://github.com/rust-lang/rust/compare/master...panicbit:portability) has shown that the current API can't really be captured in traits. That is quite dated by now. I've tried a [new approach](https://github.com/panicbit/rust/issues/2) which is a...

@jethrogb Well, the abstract_platform approach is all about being able to use things from `std` without using `std`, so the suggested changes would reduce the amount of boilerplate in the...

@Ericson2314 Indeed, the only platform-dependent use I could find was in a test in [sys_common/net.rs](https://github.com/rust-lang/rust/blob/3b6412b94324b10f698a18ea5766ef6ff8921ae8/src/libstd/sys_common/net.rs#L613-L628)

@chpio We want something like that (see #17)

To implement `DeserializeAs` and `SerializeAs` in this situation, one can simply use the derived `Deserialize` and `Serialize` impls by using `Metadata` / `Metadata` and repacking the types as needed: ```rust...