Age | Commit message (Collapse) | Author |
|
Update MSRV: 1.70.0 -> 1.75.0
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
CI speed optimization
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
chore: Update dependencies (`Cargo.toml`)
|
|
deserialize: strings: Introduce Unreachable type
|
|
No longer ignore Cargo.lock
|
|
Consistently omit patch version.
Signed-off-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
|
|
This allows us to remove a lot of code that contains calls to
unreachable! (ie, a runtime panic) with code that demonstrates, in a
way that's checked by the compiler, that the call cannot happen.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
This saves a bit of execution time.
There's no point in running MSRV and stable, because there shouldn't be
a difference. So we opt for stable because it tends to be faster.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
The nextest runner does not help enough to be viable. Installing it
takes more time than the runner saves, so go back to the normal test
runner with this patch.
This reverts commit 284de85f4e16f28caece29ae7ae3aa41b48afa54.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
The test phase is the slowest, because it actually produces binaries
for running tests.
So do not depend on the "check" phase, so that the test phase starts as
soon as possible, to speed up overall CI time.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
This is another attempt at increasing the CI speed. It does so by
removin the dedicated example checking phase, by putting all checks in
one phase (examples, tests) and run that phase only for MSRV.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Same as with the mutable "stable" being removed from our CI, we run beta
toolchain CI stuff, but we should no longer allow a changing beta
version break our CI "randomly".
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
If stable updates and introduces a new lint for example, that could
break our CI "randomly".
Thus, we do no longer depend on a mutable version of the toolchain, but
on a fixed one (that now has to be updated regularly, of course).
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
We do not get any benefit from running CI with the nightly toolchain.
We still run it with beta, so that should catch some errors if there are
any.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
There's no point in running it with two versions, and MSRV should
suffice.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
The comment says it all.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Prepare release 0.14.x
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
matthiasbeyer/fix-cargo-check-external-types-nightly-version
Fix: cargo-check-external-types must use nightly 2023-10-10
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Check external types
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
mehcode/dependabot/github_actions/actions/setup-python-5
Bump actions/setup-python from 4 to 5
|
|
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v4...v5)
---
updated-dependencies:
- dependency-name: actions/setup-python
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
deserialize: strings: Introduce string_serialize_via_display macro
|
|
Unify deser impl (redux)
|
|
This removes a lot of duplicated code.
It could be even shorter if we were to use the `paste` crate.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
This had open-coded copies of the impl for Value. Replace them with
calls to the impl for Value. This reduces duplication. It would
allow us to change the impl for Value.
Use a macro for the many very-similar functions.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
This tests, in particular, that the error messdage is as expected
including the right key and filename.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
Fix docs warnings
|
|
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Fix nested arrays (by reworking array handling)
|
|
Hide and deprecate AsyncConfigBuilder
|
|
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
This struct seems to be a remnant of a previous approach to async.
It cannot be used, and the documentation was lies.
There isn't a `build` method. There are, in fact, no methods at all.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Add DCO
|
|
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
Change the representation of our "current location". Previously it
was a list of increasingly-long full paths, but excepting the putative
final array index.
Now we just record the individual elements. and assemble the whole
path just before calling .set(). This saves a little memory on the
whole since the entries in keys are now a bit shorter.
It is much less confusing. (There are perhaps still further
opportunities to use Rust's type system to better advantage to
eliminuate opportunities for bugs.)
Arrays that appear other than at the top level are now handled
correctly. This includes nested arrays, and arrays containing
structs, etc.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|