Should JSON marshal and unmarshal functions be moved to Dasgo?

[switchupcb]

With the introduction of the Flags type (to address #53), an inconsistency is made apparent with regards to the decoupling of dasgo types to their respective MarshalJSON and UnmarshalJSON functions. This inconsistency can be addressed by moving the code defined in the following files to dasgo.

• https://github.com/switchupcb/disgo/blob/v10/wrapper/json_marshal.go
• https://github.com/switchupcb/disgo/blob/v10/wrapper/json_unmarshal.go
• https://github.com/switchupcb/disgo/blob/v10/wrapper/json_unmarshal_convert.go

This change would move the responsibility of JSON marshal and unmarshal functions to dasgo. In doing so, these functions would be maintained by the maintainers of dasgo which is reviewed by multiple Go Discord API Wrappers. This reduces the overhead of maintaining this code from disgo maintainers to dasgo maintainers at the cost of standardization.

All code from dasgo continues to be optional to use. However, it would be recommended— upon approval of this change — to stick to the function definitions defined by dasgo. Such that the cost of standardization would be using dasgo JSON marshal and unmarshal error messages or decision to panic, but nothing else.

This change would NOT effect the performance of disgo.

[switchupcb]

This poll will be closed upon the introduction of the Discord API v11.

[switchupcb]

The poll has been closed early to anticipate the update schedule: The result is yes, JSON marshal and unmarshal functions will be moved to Dasgo.

[switchupcb]

Operation aborted during implementation: Too many API Wrapper specific details in JSON marshal and marshal function implementations.