Skip to content

Add namespacing for Core and PSA structures #35

Open
@hug-dev

Description

@hug-dev

With #30 in, there is a clear separation of Core and PSA structures with the Psa or psa_ prefix added everywhere.
A better idiomatic and scalable way at separating them would be to use namespacing.

In the operations, the Core and PSA files would be in their own folders.
In the interface, Core and PSA structures would be in their own module. There would be enumerations of PSA operation opcodes and Core operation opcodes with an Opcode enum of those enum at the top. Same for the ResponseStatus.

The Provide trait contains Core and PSA operations. One option could be to have two Provide traits: PsaProvide and CoreProvide.

This issue is mainly for discussion on those topics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestlargeEffort label

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions