Rpc service parsing

[mattiekat]

Progress tracked by
https://github.com/RainwayApp/bebop/projects/2

Follows #177

[lynn]

I think we should throw an extra delimiter between the service name and function name for good measure, so that _User_ListAdd and _UserList_Add or something won't clash.

[lynn]

It might be cool to make some helper methods for this, like

private static string RpcNamePrefix(string serviceName, string name)
    => $"_{serviceName.ToPascalCase()}_{name.ToPascalCase()}";

private static string RpcReturnStructName(string serviceName, string name)
    => RpcNamePrefix(serviceName, name) + "Return";

just in case we change our minds about e.g. the Pascal-casing.

[mattiekat]

Two things on this

1. I assume that the different languages will convert to whatever name capitalization makes sense for them (e.g. Rust will use pascal for structs no matter what the name here is and snake case for functions) if they care
2. You are right that another delimiter is technically needed, but a _ might be problematic because of the previous point.

Since the structs are not really to be used by the end user we could just uglify them a bit and use something like "_Service{serviceName}Function{functionName}" even. All that matters is we know what it is when we go to generate code.