Optimize augment conflict checking 41/69241/2
authorRobert Varga <robert.varga@pantheon.tech>
Thu, 8 Mar 2018 01:12:43 +0000 (02:12 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Thu, 8 Mar 2018 09:55:59 +0000 (10:55 +0100)
commit3ca3fc462aec22eb2dec19066edafbb039cb2a84
treec3ab3fe2b163763cb2f19e6de7a4883426badac0
parent45eec389967fa56aef4c9dd45dae3313418e6504
Optimize augment conflict checking

When we are validating whether a node can be introduced, we end up
needlessly iterating when the source is not a DataDefinitionStatement
and also end up running comparison when a substatement is not a
DataDefinitionStatement,

Refactor the code to take these invariants into account.

Change-Id: Ie55c7dfebacfad1189de1929c23809fd284958b4
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit 6e4ed947d08856771dbbdf428ba84c44aed45126)
yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/stmt/rfc6020/AugmentStatementImpl.java