Antoni Spaanderman

i found a similar issue when making this report: ```rust let mut v = [3, 2, 1, 0]; let tmp = v[0]; v[0] = v[1]; v[1] = tmp; println!("tmp: {tmp}");...

i get this error when using the [netcat example](https://github.com/romanz/electrs/blob/master/doc/usage.md#rpc-examples) i get the right response, but netcat doesn't return the command prompt after receiving the data, so i kill it with...

+1 related to #765 but that pr in inactive (sent a message a year ago but no development since then there) rust trait are really good for this, would be...

is this PR still being worked on? i think it would be useful to allow for different databases (maybe helps to optimize for hdd/ssd performance), but instead of choosing one...

how is this pr going? are you still working on it, and which things are still missing/planned (like the ones you named [here](https://github.com/romanz/electrs/pull/765#issuecomment-1232170746), but maybe more)?

might be worth to define all error codes (in a new enum) to allow for easy future mapping of them to a different or more verbose message (like this pr)

The enum members don't need the `i32` fields, they will only every be set to one value define them like this: ` RpcInvalidRequest = -32600,` and the enum definition and...

the documentation of the error codes can also be copied from the header file of bitcoind source i meant something different with macro generated (`macro_rules! ...`), but maybe thats just...

> Are you referring to the comments in the protocol.h file? yes > Can I generate a from_i16 implementation on the enum with just declarative macros (`macro_rules!`)? yes with something...

> @antonilol Thanks for your help with the `macro_rules!` definition. I've changed the implementation to use that and I also added doc comments. Please take a look and let me...