Skip to content

Problem: Draft APIs still exist in version 1.x despite documented code #334

@BHare1985

Description

@BHare1985

Following the discussion at #214 it seems like there was consensus that there should be no draft APIs as of 1.0, and 1.1 was suppose to fix this issue. However, I still believe draft APIs are being auto-configured as on in 1.1, which is confusing if someone was to fork this project and actually want to use draft APIs.

There are numerous places in the documented code that reference certain features being DRAFT APIs, e.g. https://github.com/zeromq/malamute/blob/master/src/mlm_selftest.c#L35

Are there any plans to actually mark the classes in version was as not draft?

This confused me as I originally thought I didn't have all the draft APIs so i re-built with the proper configure command only to find out that I had the draft after all. These conventions are meant to help, not hinder this type of stuff.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions