Skip to content

Use OQS_*_set_callbacks instead of C_OR_NI_OR_ARM macros #1842

@SWilson4

Description

@SWilson4
          This isn't something to change in this PR, but something I noticed just from looking at this code during review.  Now that we have the ability to set callbacks, could we get rid of the `C_OR_NI_OR_ARM` macros and instead set the callbacks once (either during library init, or alternatively on first use if it's not set)?  Again: not something to do in this PR, but if anyone else thinks it might be good, we could create a separate issue to track.

Originally posted by @dstebila in #1707 (comment)

See also: #1599, #1832

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueIssue for new contributorsrefactorReorganizing existing code

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions