4 releases
0.1.3 | Jun 13, 2022 |
---|---|
0.1.2 | Jun 8, 2022 |
0.1.1 | Jun 8, 2022 |
0.1.0 | Jun 7, 2022 |
#1850 in Procedural macros
238 downloads per month
8KB
121 lines
Unpattern
Unbox and declare a variables from the pattern with easy syntax.
Sometimes, it is needed to unbox an enum even you know what the enum exactly matches,
however you must use match
or if let
expression to unbox it.
For example:
enum TestEnum {
Int(i32),
Tuple(i32 i32),
}
let test = TestEnum::Int(3);
// You need to unbox the enum.
if let TestEnum::Int(v) = test {
assert_eq!(v, 3);
} else {
unreachable!();
}
This crate helps to unbox the enum from a pattern.
let test = TestEnum::Int(3);
unpat!(TestEnum::Int(v) <- test); // `v = 3` binding is created here.
assert_eq!(v, 3);
The concept of the crate is inspired from Elixir's pattern matching.
test = %Test{a: 1, b: 2}
%Test{a} = test # `a = 1` binding is created here
Usage
struct TestStruct {
int: i32,
tuple: (i32, i32),
}
enum TestEnum {
Int(i32),
Tuple(i32, f64),
Struct(TestStruct),
}
let test = TestEnum::Struct(TestStruct {
int: 1,
tuple: (2, 3),
});
unpat!(
TestEnum::Struct(
TestStruct { int, tuple: (x, y) }
) <- test
);
assert_eq!((int, x, y), (1, 2, 3));
Also, the named field can be bound with the @
syntax.
unpat!(
TestEnum::Struct(
TestStruct { int, tuple: v @ (x, y) }
) <- test
);
assert_eq!((int, x, y), (1, 2, 3));
assert_eq!(v, (2, 3));
Error Handling
unpat
panics if the pattern doesn't match. If you want to handle the error, use try_unpat
instead.
let test = TestEnum::Int(3);
try_unpat!(TestEnum::Int(v) <- test, String::from("The pattern doesn't match"));
assert_eq!(v, 3);
// The pattern doesn't match. It will return Err.
try_unpat!(TestEnum::Tuple(a, _) <- test, String::from("The pattern doesn't match"));
unreachable!()
TODO
- Implement all patterns
- Caret syntax
Related works
- StackOverflow question: #
- enum-as-inner
- RFC-349
Dependencies
~1.5MB
~37K SLoC