Unify terms regarding assembly form to use generic vs. custom
authorLei Zhang <antiagainst@google.com>
Wed, 23 Jan 2019 19:26:56 +0000 (11:26 -0800)
committerjpienaar <jpienaar@google.com>
Fri, 29 Mar 2019 22:32:35 +0000 (15:32 -0700)
commit565445085300c549e63c1ef254c35f0dae5d23f4
tree574b33f66c5fdb810bc953b34a7e8a90d0f15ff9
parentb28009b681a45a0e5b925ed90f33f8285c87e6af
Unify terms regarding assembly form to use generic vs. custom

This CL just changes various docs and comments to use the term "generic" and
"custom" when mentioning assembly forms. To be consist, several methods are
also renamed:

* FunctionParser::parseVerboseOperation() -> parseGenericOperation()
* ModuleState::hasShorthandForm() -> hasCustomForm()
* OpAsmPrinter::printDefaultOp() -> printGenericOp()

PiperOrigin-RevId: 230568819
mlir/g3doc/LangRef.md
mlir/g3doc/OpDefinitions.md
mlir/g3doc/Rationale.md
mlir/include/mlir/IR/OpDefinition.h
mlir/include/mlir/IR/OpImplementation.h
mlir/include/mlir/LLVMIR/llvm_ops.td
mlir/include/mlir/StandardOps/StandardOps.h
mlir/include/mlir/StandardOps/standard_ops.td
mlir/lib/IR/AsmPrinter.cpp
mlir/lib/IR/Operation.cpp
mlir/lib/Parser/Parser.cpp