recap
recap copied to clipboard
softprops
deserialize typed structures from regex captures
## 💡 Feature description Currently the code generated by `#[derive(Recap)]` doesn't seem to be able to be composed in any manner. Ideally, I would more or less expect that fields...
## 💡 Feature description It would be nice to be able to capture referenced data, like a more general `Deserialize` which does permit borrowing. I would think `recap::from_captures` could just...
## What did you implement: This allows adding a `#[recap(delimiter_regex = "...")]` attribute to a field with a sequence-type value which is used when splitting the string. Currently the string...
## What did you implement: This enables Recap to work for multiple layers of nested structs, as seen in the `custom_deserialize_allows_nested_structs` test. The impetus for this came from things like...
This would enable amortizing allocations around building `Captures`. https://docs.rs/regex/latest/regex/struct.CaptureLocations.html
The dep on envy is unnecessary, and its error variants don't particularly make sense for here. Instead, I would expect something like: ```rust enum Error { RegexDoesNotMatchInputString, DeserializationError{ ... }...
On nightly compiler, I'm getting: ``` --> y2015\src\bin\solution_2015_09.rs:10:30 | 10 | #[derive(Debug, Deserialize, Recap, Clone)] | ^---- | | | move the `impl` block outside of this constant `RECAP_IMPL_FOR_Route` 11...
## What did you implement: Replaces `Result` with `std::result::Result` in the derived code. Why: had errors because of `type Result = std::result::Result` (a common thing to do). We really should...
