Strict parsing for core

[tomusdrw]

Some types in Response were missing deny_unknown_fields that would cause invalid response to be parsed correctly when Deserializing.

However later I started thinking if having a less strict version would be useful as well, hence I introduced the strict feature.

I'd like to hear your opinions on whether we want to maintain strict and non-strict versions or rather default to strict.

See: tomusdrw/rust-web3#222 (comment) why non strict mode would be useful.

[debris]

I like strict more... jsonrpc provides a way to send arbitrary data in a params field, so I don't see a reason why someone would need to use other fields

[tomusdrw]

@debris Yeah, I'm more inclined to go with strict-only, but wanted a second confirmation. Note that this will break compatibility with servers/clients that add some stuff to the response/request objects (one example of this is linked in the description).

[ascjones]

Looks good. Agree about strict

[jez]

I opened a follow up issue here:

#595