v3.0.0 Request For Comment

[markus-wa]

For some background:
In the coming months we will be moving away from the deprecated v1 ProtoBuf API to v2, this also includes moving from the unmaintained gogo/protobuf project to vtprotobuf

I suspect this will be an API breaking change, warranting a v3.0.0 release.
There is also a chance we will change some APIs to use go 1.18 features, namely generics (maybe also fuzzing for tests).

This is a Request For Comment for the following:

• questions about the migration
• concerns about vtprotobuf
• concerns about go 1.18
• suggestions for changes/improvements we could include in this release (specifically improvements that are API-breaking)
• anything else you think may be relevant to a major version bump or new release

further reading:

• https://go.dev/blog/protobuf-apiv2
• GoGo Protobuf looking for new ownership gogo/protobuf#691
• https://vitess.io/blog/2021-06-03-a-new-protobuf-generator-for-go/
• https://go.dev/blog/why-generics

[markus-wa]

current scope:

• go 1.11 -> go 1.18 migration
• gogo/protobuf -> vtprotobuf migration
• ? removal of /assets and /pkg/demoinfocs/metadata - the value proposition of this is superseded by https://github.com/saiko-tech/csgo-centrifuge
• move /internal/constants to /pkg/demoinfocs/constants - some consumers rely on some of these constants
• remove deprecated parts of the API
• make certain functions accept generic type arguments (e.g. Parser.RegisterEventHandler())