ASTWriterDecl.cpp File Reference

#include "clang/Serialization/ASTWriter.h"
#include "ASTCommon.h"
#include "clang/AST/DeclCXX.h"
#include "clang/AST/DeclContextInternals.h"
#include "clang/AST/DeclTemplate.h"
#include "clang/AST/DeclVisitor.h"
#include "clang/AST/Expr.h"
#include "clang/Basic/SourceManager.h"
#include "clang/Serialization/ASTReader.h"
#include "llvm/ADT/Twine.h"
#include "llvm/Bitcode/BitstreamWriter.h"
#include "llvm/Support/ErrorHandling.h"

Include dependency graph for ASTWriterDecl.cpp:

Go to the source code of this file.

Classes
class	clang::ASTDeclWriter
Namespaces
namespace	clang
Functions
static bool	isRequiredDecl (const Decl *D, ASTContext &Context)

---

Function Documentation

static bool isRequiredDecl	(	const Decl *	D,
		ASTContext &	Context
	)		[static]

isRequiredDecl - Check if this is a "required" Decl, which must be seen by consumers of the AST.

Such decls will always be deserialized from the AST file, so we would like this to be as restrictive as possible. Currently the predicate is driven by code generation requirements, if other clients have a different notion of what is "required" then we may have to consider an alternate scheme where clients can iterate over the top-level decls and get information on them, without necessary deserializing them. We could explicitly require such clients to use a separate API call to "realize" the decl. This should be relatively painless since they would presumably only do it for top-level decls.

Definition at line 1928 of file ASTWriterDecl.cpp.

References clang::ASTContext::DeclMustBeEmitted().