//! Conflicts the file states and the tree had to resolve.
use EntityId;
/// A second parent the schema forbids, recorded instead of silently dropped.
///
/// Both `IfcElement.ContainedInStructure` and `IfcObjectDefinition.Decomposes`
/// are `SET [0:1]`. A file naming two parents is malformed; the first
/// relationship processed wins so the tree stays a tree, and the loser is
/// reported here. Every view of the tree agrees with the kept answer.