rust_sqlite VS medium-unlimited

You may have noticed that throughout the entire code I am making reference to a SQLRiteError type. That is an error type I defined as an enum using the thiserror crate, that is a super easy to use library that provides a convenient derive macro for the standard library’s std::error::Error trait. If you check the commits in the github repository, you may notice that I first wrote my own implementation of the std::error::Error trait. But then I bumped into this trait, that basically takes care of a lot of the boiler plate, and let’s face it, the code looks super clean! This is our error module so far, located in src/error.rs .

Also check out the github repo: https://github.com/joaoh82/rust_sqlite

I assume that if you are trying to follow this and writing some code along with me you can manage to create an empty Rust project on your own. Just to be clear this is what I did to start: cargo new rust_sqlite --bin . But again, you can find all the code on Github.

View on Github (pull requests are welcome)

https://github.com/manojVivek/medium-unlimited & https://scribe.rip/ & https://github.com/und3fined/medium-unlocker - Unlimited Articles on Medium.

In this way you don't have as granular control. Use Medium Unlimited extension.

Here

Check this out - https://github.com/manojVivek/medium-unlimited

Agree with you about medium ! Try this https://github.com/manojVivek/medium-unlimited

I just use Medium Unlimited and I've never had that problem again! It even works on other website :)