See also linebender/vello#439
This should open the door to doing much more comprehensive testing at
higher level in the nearish future (including e.g. in `xilem_masonry`)
There is one "semi-false-positive" lint triggered, which I have fixed.
Otherwise, the required
```
cargo upgrade --ignore-rust-version
cargo update
```
This was remarkably painless.
I especially appreciate @taiki-e providing an install-action which does
90% of the CI work for us.
---------
Co-authored-by: Daniel McNab <36049421+DJMcNab@users.noreply.github.com>
Supercedes https://github.com/linebender/xilem/pull/411
This is designed with #417 in mind, to not lock-in to our event loop.
---------
Co-authored-by: Philipp Mildenberger <philipp@mildenberger.me>
This was most recently updated in
https://github.com/linebender/vello/pull/505
The main differences are:
1) Greater concurrency between clippy and testing
2) More explanations
3) MSRV checking
4) Use of `cargo hack`
5) WASM checked in CI
I've also added the current values of our MSRVs to the main three
crates.
Currently, the only legit typo being found is `seeked` but I'm not sure
what to do about that.
Would be nice to check for new typos in CI anyways, right?
---------
Co-authored-by: Kaur Kuut <strom@nevermore.ee>
* Add the Linebender standard copyright header to all Rust source files.
- Copyright year is based on the original file creation date.
- Files that are based on other projects, mostly Druid, get the correct
credit.
- Files that were built from scratch for Xilem but had copy-pasted Druid
headers get those headers corrected.
* Add copyright header check to CI.
* Add dedicated `LICENSE` files to each package to ensure it is part of
the crates.io source distribution.
* Add `AUTHORS` file to list most of the top contributors.
- It does not need to be complete and additional entries are welcome via
PRs.
* Create a minimal xilem_masonry
* Add a first draft of view sequences
* Implement a flex view
* Fix clippy
Some of these suggestions are kind of bad
but that's by-the-by
* Update CI to 1.77
* Skip masonry docs in CI
* Clippy, again
* Fix clippy
* Skip render snapshot tests
* Skip testing which needs rendering on CI
* Add tuple sequences
* Address review comments and clippy
We don't deny warnings in CI because we currently have warnings.
Once #1 lands, we can enforce cleanliness from warnings
See also d0b9e1905c
as we only use windows at the moment
Jared O'Connell