dmxus VS copygen

This will be quite niche, but I develop an open source JavaScript library for manipulating DMX lighting fixtures. The library is called dmxus and is a library which aims to provide an API for controlling DMX lighting fixtures in with conventions that feel similar to working on a typical lighting controller or console. I actively develop it for use with a popular industry DMX interface, but if I were to have a small infusion of cash, I would add support for a few other commonly used interfaces on the market.

Copygen is a type-based code generator for the Go programming language. Copygen allows developers to generate type-to-type copy functions out-of-the-box without reflection (why?), but it can also be used to generate code. As an example, disgo is a performant, secure, and thread-safe Go Discord API Wrapper that uses Copygen with dasgo to achieve feature completion.

An alternative is to use a reflection based struct copier library or a codegen struct copier library

Disgo is the only Go API Wrapper using a maintainable approach to become feature complete. Disgo is the only Go API Wrapper to provide OAuth2 flows. Disgo is the only wrapper to define API definitions (objects, requests, commands) as structs, allowing for usage of the Discord Producer API without requiring knowledge of an additional API Wrapper Consumer API.

Copygen allows developers to define types, structs, and more in its setup.go file and has no issues copying them to the output; except for comments. The Go AST makes it "very difficult to update the AST and retain correct comment place (from 2017)" and is not likely to change any time soon. As a result, Copygen sometimes generates free-floating comments (i.e multi.go). Copygen's comments are handled in its Parser. Feel free to use any necessary libraries or rewriting of the comment-parsing mechanism to fix this issue.