@@ -82,10 +82,10 @@ impl ItemCanonicalPath for ItemId {
82
82
/// module, a type, a function, or a variable (see `ItemKind` for more
83
83
/// information).
84
84
///
85
- /// Items form a tree , and each item only stores the id of the parent.
85
+ /// Items form a graph , and each item only stores the id of the parent.
86
86
///
87
- /// The root of this tree is the "root module", a meta-item used to hold all the
88
- /// top-level items.
87
+ /// The entry-point of this graph is the "root module", a meta-item used to hold
88
+ /// all the top-level items.
89
89
///
90
90
/// An item may have a comment, and annotations (see the `annotations` module).
91
91
///
@@ -163,8 +163,8 @@ impl Item {
163
163
/// they aren't.
164
164
///
165
165
/// This function is used to determine when the codegen phase should call
166
- /// `codegen` on an item, since it's assumed that any item that is not
167
- /// top-level will be generated by its parent.
166
+ /// `codegen` on an item, since any item that is not top-level will be
167
+ /// generated by its parent.
168
168
pub fn is_toplevel ( & self , ctx : & BindgenContext ) -> bool {
169
169
// FIXME: Workaround for some types falling behind when parsing weird
170
170
// stl classes, for example.
@@ -610,9 +610,8 @@ impl ClangItemParser for Item {
610
610
Self :: from_ty_or_ref_with_id ( ItemId :: next ( ) , ty, location, parent_id, context)
611
611
}
612
612
613
- /// Parse a type, if we know it before hand, or otherwise store it as an
614
- /// `UnresolvedTypeRef`, which means something like "a reference to a type
615
- /// we still don't know".
613
+ /// Parse a C++ type. If we find a reference to a type that has not been
614
+ /// defined yet, use UnresolvedTypeRef as a placeholder.
616
615
///
617
616
/// This logic is needed to avoid parsing items with the incorrect parent
618
617
/// and it's sort of complex to explain, so I'll just point to
0 commit comments