Skip to content

enh(versioning): setup a major minor macro #90

@HaoZeke

Description

@HaoZeke

..or even a major minor patch version macro. The reasoning is simple, better integration. The current design of having no version for a header only library AFAIK is not a good practice at all. The argument that downstream users shouldn't have to update also doesn't really hold water, generally libraries get updated when there's a major version bump.. plus Hyrum's law

Some other libraries with versioned headers:

  • Boost
  • json.hpp
  • fmt

These are mostly all C++ ones, but then there's also:

and a slew of them, these are OTOH, and build systems with a simple .in file should make setting this painless.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions