The `cleanup` flag is only available on [dpl v2] which is opt-in. Moreover, dpl v2 defaults to `cleanup: false` anyway so there is no need to specify it.
[dpl v2]: https://docs.travis-ci.com/user/deployment-v2
cc #224
* Add an off-by-default 'unstable' flag
* Remove explicit web framework feature names
Having forgotten that deps and features can't have the same name,
attempts to better document all the features in one place were
misplaced.
* Split up tests on Travis
`cargo test` doesn't allow `--workspace` and `--features`
simultaneously, so we're forced to test each package separately in order
to manually specify features (or in this case, test everything but
unstable)
* Update Travis Config
- Document the state of Cargo workspaces and features
- Update the benchmarks to trickle down the 'unstable' feature
* Use `std::matches!`
- Remove crates.io `matches` in favor of the `std` version
- Fix Clippy warning by changing a `match ... { ... }` to
`matches!(...)`
* Satisfy `blocks_in_if_conditions`
* Add proc_macro2 and quote dependencies
* Completly switch over to proc_macro2 where possible
* Remove unessesary ::from casts
* Remove pendantic cast that i missed
* Make Builder::push_tokens accept TokenStream
* Remove stray commented out code
* Reword unclear comment on `Span` to a todo item
* Move comment closer to its intended line
* Use into instead of explicit conversion
As discussed in Pull Request #182 we will only support actix-web 2.0.0
from this point onwards. If you still wish to use a previous version of
actix-web you'll have to pin the version.
In order to support both actix-web < 2.0.0 and >= 2.0.0 at the same
time I added a feature actix-web-2, which enables the actix-web
dependency with the respective version und the name active-web-2-dep
and the futures dependency which is required(?) for implementing the
Responder trait for >= 2.0.0.
Thus the user of maud has the choice to use actix-web in the version
they prefer.
