-
Notifications
You must be signed in to change notification settings - Fork 34
Conversation
@liamsi utACK |
@liamsi yes, when I run
|
@liamsi also, the compiler spits out a lot of warnings about the generated files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks ok.
@liamsi I'm not yet sure about #70 -- perhaps Cargo.lock could still be .gitignored in top / library crate, but the "examples" could be moved to application example crates with Cargo.lock that would be also built, so that there's both flexibility allowed and some level of determinism checked?
or commit the diff in generated files and have the top-level Cargo.lock for the mentioned tests: #36 ? |
could possibly be in a workspace? |
We should merge #77 first and update this PR |
I like the idea of having a separate crate for the examples (which contains a lock file) 👌 |
updated edition in #85 |
Very small PR that just makes the code 2018 edition compatible (followed this: https://doc.rust-lang.org/edition-guide/editions/transitioning-an-existing-project-to-a-new-edition.html).
@tomtau: when I run cargo build, I see changes in the proto generated rust files (nothing relevant, only in
file_descriptor_proto_data
). Mind checking out that branch and runcargo build
on your machine. Do you also see changes in the abci.rs, merkle.rs, types.rs?ref: #60 #74 #70
- [ ] Wrote tests- [ ] Updated relevant documentation (docs/
)- [ ] Added a relevant changelog entry:clog add [section] [stanza] [message]
Files changed
in the github PR explorer- [ ] Bump Tendermint & ABCI version in README.md if version was updatedFor Admin Use: