[all-commits] [llvm/llvm-project] 35f55f: [mlir][ODS] Consistent `cppType` / `cppClassName` ...

[Matthias Springer via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 35f55f53dfbb62902da007f308a618192102dd1c
      https://github.com/llvm/llvm-project/commit/35f55f53dfbb62902da007f308a618192102dd1c
  Author: Matthias Springer <me at m-sp.org>
  Date:   2024-08-09 (Fri, 09 Aug 2024)

  Changed paths:
    M mlir/include/mlir/IR/AttrTypeBase.td
    M mlir/include/mlir/IR/CommonAttrConstraints.td
    M mlir/include/mlir/IR/CommonTypeConstraints.td
    M mlir/include/mlir/IR/Constraints.td
    M mlir/include/mlir/TableGen/Type.h
    M mlir/lib/TableGen/Type.cpp
    M mlir/lib/Tools/PDLL/Parser/Parser.cpp
    M mlir/tools/mlir-tblgen/OpDefinitionsGen.cpp
    M mlir/tools/mlir-tblgen/OpFormatGen.cpp

  Log Message:
  -----------
  [mlir][ODS] Consistent `cppType` / `cppClassName` usage (#102657)

Make sure that the usage of `cppType` and `cppClassName` of type and
attribute definitions/constraints is consistent in TableGen.

- `cppClassName`: The C++ class name of the type or attribute.
- `cppType`: The fully qualified C++ class name: C++ namespace and C++
class name.

Basically, we should always use the fully qualified C++ class name for
parameter types, return types or template arguments.

Also some minor cleanups.

Fixes #57279.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications