rmsyn

We could also potentially add a `mask` parameter to describe the bitmask of readable/writable fields (or two masks if those sets are not identical). Adding a `mask` parameter(s) would allow...

> I would prefer to leave as less dependencies as possible in riscv Agreed, I just included it because it reduces the verbosity of the macro call. > Regarding the...

> What do you think? Sounds good to me, I'll add some things we discussed here, and open a PR.

> Using custom types (mainly enums) for setters and getters. We could add another branch that takes an `$var_ty: ident, [$($variant:ident, $variant_val:literal),*]$(,)`. That would allow to define a custom `enum`...

> I can try to work something out. I added the `enum` branches, and an extra helper macro. Let me know what you think.

Updated the changes onto the latest HEAD commit. Squashed the previous fixup commit to simplify review. Added the necessary changes to incorporate the addition of fallible functions, and changed the...

@romancardenas I added some more fixes + improvements to the macro helpers. Reduced some redundancy, and hopefully made the macro invocations more readable. Please let me know what you think....

> Looks good, but it is true that having to do something like: > > ```rust > field: { > /// Gets the `cycle[h]` inhibit field value. > cy, >...

> Looking at this specific example, the macro calls other macros (`csr`, `read_csr_as`, and `read_only_csr_field` a few times). So what is the benefit of having a single macro with many...

> Let's first figure out how we want to use the macros and then we can explore using the paste crate (which looks great, by the way). I've moved the...