Skip to content

Guidelines/philosophy for new operations, including security principles #242

@quidity

Description

@quidity

The universe of operations supported by this spec is likely to grow in the future.

To ensure that new operators are shaped in a way that they can be implemented securely, it would be good to include some general guidelines/philosophy on how ops are defined to reduce potential for ops to result in implementation problems.

For instance, avoid reshaping tensors, simplicity of arguments, no parsers for complex data formats.

Metadata

Metadata

Assignees

No one assigned

    Labels

    security-trackerGroup bringing to attention of security, or tracked by the security Group but not needing response.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions