Do not use json.RawMessage for untyped request arguments

[dottedmag]

Using json.RawMessage for request arguments makes the users of go-dap unnecessary cumbersome. any would be a better choice. Compare

msg, err := json.Marshal(someArgs)
if err != nil {
    ....
}
AttachRequest {
	Arguments: json.RawMessage(msg),
}

and

AttachRequest {
        Arguments: someArgs,
}

[corneliusweig]

I don't quite agree. In fact I suggested to treat more submessages as RawMessage (#88).

With any or map[string]any submessages I need to do a lot of type casting when accessing fields in that message. This is cumbersome and error-prone. Instead, when there is a RawMessage, I can Unmarshal the message into a user-defined type of my choice. Then accessing fields in this submessage is type-safe and easy.

So I think that RawMessage is much more type safe and easier to handle.

[dottedmag]

This is for request arguments.