Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use consistent phrasing for operator creation #674

Merged
merged 4 commits into from
May 10, 2024

Commits on May 3, 2024

  1. Use consistent phrasing for operator creation

    Places that create ops use an inconsistent mixed of simple phrases,
    camelCase, Title Case, ACRONYMS, and "quoted strings". The most common
    was camelCase, but the wording can be weird, and the bulk-defined
    binary/unary/logical/pooling/reduction ops and activations use a
    "quotedCamelCase", so I went with that.
    
    See webmachinelearning#591 (comment)
    for the most commentary.
    
    Resolves webmachinelearning#572
    inexorabletash committed May 3, 2024
    Configuration menu
    Copy the full SHA
    8b3153d View commit details
    Browse the repository at this point in the history

Commits on May 6, 2024

  1. Configuration menu
    Copy the full SHA
    73fe3b6 View commit details
    Browse the repository at this point in the history

Commits on May 7, 2024

  1. Configuration menu
    Copy the full SHA
    75348cb View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ca5cf52 View commit details
    Browse the repository at this point in the history