• Write reproto comments out into the generated code.
• Customize the name of the package for which the generated code should be put in, or if each module should have its own package.
• Follow coding conventions, this will require extending genco.
  • Indentation.
  • Spacing between statements.
  • Best-practices for handling interfaces.
• [ ]

Is your request related to a problem? Please describe.
Model::add_shape has to determine if any existing unresolved shape exists and merge, not overwrite.

The Smithy spec says...
It doesn't say, the behavior has to be inferred

Additional context
Add any other context or screenshots about the feature request here.

There is support for primitive type constants/literals (e.g. integers, floats, strings, etc.) as introduced by @jb090979.

This can be used as a base for introducing complex type constants (e.g. arrays, structures, maps, etc.).