Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to 2018 edition and prune dependencies #63

Merged
merged 2 commits into from Oct 17, 2019

Conversation

johnchildren
Copy link
Contributor

@johnchildren johnchildren commented Oct 5, 2019

Update the project to 2018 edition in both code and documentation for
usage, prunes unused dependencies and removes dependency on failure,
preferring the std Error trait.

There was also a misleading error message about not being able to find a
temporary file directory, which would have actually have been caused by
a failure to encode a filepath into UTF-8
(https://doc.rust-lang.org/src/std/path.rs.html#1848-1850). However this
error should not happen anyway by just using the PathBuf directly to
make the full path for the persisted file output.

Should resolve #57

Choose one: is this a 馃悰 bug fix, a 馃檵 feature, or a 馃敠 documentation change?
Feature and docs

Checklist

  • tests pass
  • tests and/or benchmarks are included
  • documentation is changed or added

Context

#57

Semver Changes

Should take a minor bump potentially, but no changes to APIs.

Update the project to 2018 edition in both code and documentation for
usage, prunes unused dependencies and removes dependency on failure,
preferring the std Error trait.

There was also a misleading error message about not being able to find a
temporary file directory, which would have actually have been caused by
a failure to encode a filepath into UTF-8
(https://doc.rust-lang.org/src/std/path.rs.html#1848-1850). However this
error should not happen anyway by just using the PathBuf directly to
make the full path for the persisted file output.
@johnchildren
Copy link
Contributor Author

I notice there isn't a CONTRIBUTING.md in the repo, is there one somewhere else I can look at?

@johnchildren
Copy link
Contributor Author

Should note that the test failures are due to rust versions that do not support 2018 edition in the matrix - I could remove them or update to a more recent version?

@Profpatsch
Copy link

Profpatsch commented Oct 16, 2019

This repository seems unmaintained, pinging members of the rust-cli organization: @matthiasbeyer @codesections @Dylan-DPC @XAMPPRocky

@codesections
Copy link
Member

Thanks for the ping. I haven't personally been involved with this repo; if this thread doesn't get a reply soon, I'll raise the issue of this repo's status in our next meeting.

@Dylan-DPC-zz
Copy link

@Profpatsch this isn't unmaintained, it's just that we were focussing on the other repos for a while.

So, since we are migrating to 2018 edition, we need to update the minimum rust version in the CI. Currently the build is (expectedly) failing on 1.25 and 1.29 because those versions don't support 2018 edition. So you will have to modify it. I would prefer to bump it all the way to 1.36.0 (stable - 2)

1.25 and 1.29 do not support 2018 edition so move to 1.36 as minimum
  supported version (2 minor versions lower than current stable as of
  2019-10-17).
@johnchildren
Copy link
Contributor Author

Thank you, have updated to 1.36.0 as suggested! Tests are now passing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update to Rust 2018
4 participants