From e2e83c99947eef71d0c2d2877a2a3f58f54a58d9 Mon Sep 17 00:00:00 2001 From: Vladimir Prus Date: Wed, 31 May 2006 16:03:20 +0000 Subject: [PATCH] Clarify type naming. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@28587 91177308-0d34-0410-b5e6-96231b3b80d8 --- include/llvm/Type.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/include/llvm/Type.h b/include/llvm/Type.h index 3daafa6cac4..c79aed676d6 100644 --- a/include/llvm/Type.h +++ b/include/llvm/Type.h @@ -42,6 +42,11 @@ class TypeMapBase; /// /// Once allocated, Types are never free'd, unless they are an abstract type /// that is resolved to a more concrete type. +/// +/// Types themself don't have a name, and can be named either by: +/// - using SymbolTable instance, typically from some Module, +/// - using convenience methods in the Module class (which uses module's +/// SymbolTable too). /// /// Opaque types are simple derived types with no state. There may be many /// different Opaque type objects floating around, but two are only considered