-
Notifications
You must be signed in to change notification settings - Fork 94
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add test to assert macro hygiene for Encode and Decode derives #293
Conversation
Add tests for Decode and Encode derive proc macros.
miri is failing because of a false positive #288 (comment) |
Co-authored-by: Bastian Köcher <[email protected]>
@bkchr applied your suggestion. I just copied the code and comment from the other UI test. @thiolliere what do you mean by remove Could we do a minor release after this? It would be nice to have the latest changes in dependencies such as ink! that also has tests for |
the CI is failing, I think if we keep a ci test failing for a false positive we will never look at it again and we will miss in case another error is raised. By removing the miri test I mean this: diff --git a/src/bit_vec.rs b/src/bit_vec.rs
index 1beca32..35d3123 100644
--- a/src/bit_vec.rs
+++ b/src/bit_vec.rs
@@ -191,6 +191,10 @@ mod tests {
}
#[test]
+ // Flaky test due to:
+ // * https://github.com/bitvecto-rs/bitvec/issues/135
+ // * https://github.com/rust-lang/miri/issues/1866
+ #[cfg(not(miri))]
fn bitvec_u32() {
for v in &test_data!(u32) {
let encoded = v.encode(); |
…aritytech/parity-scale-codec into robin-add-test-for-no-implicit-prelude
The |
I don't mind another release, we can do another PR which update the changelog and version of parity_scale_codec. |
👍
Are you doing that or shall I? |
I'm not doing currently, you can do |
Uses the
#![no_implicit_prelude]
attribute to add UI tests to guardEncode
andDecode
derives against macro hygiene mistakes.This way the PR found a minor macro hygiene bug in
Decode
and fixes it.Also fixed a minor bug with
MaxEncodedLen
test.