Do not use singleton ImmutableMap for datatree/schematree 61/87261/2
authorRobert Varga <robert.varga@pantheon.tech>
Wed, 29 Jan 2020 00:39:50 +0000 (01:39 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Wed, 29 Jan 2020 12:29:20 +0000 (13:29 +0100)
commitbd432e731100aa299d5564f930efcb91e0ee57e9
treec4d0f41d096dd7c2173985c6b1b62e9bb25bc988
parent68da3668580ffc48096854d361b628358e5b59b7
Do not use singleton ImmutableMap for datatree/schematree

As it turns out singleton ImmutableMap has a few kinks, one of which
is allocating its inverse when asked for values. This is consting us
48 bytes more than with Collections.singletonMap(), hence let's
special case to bring our footprint down.

JIRA: YANGTOOLS-652
Change-Id: I7ac170c02609a15b3ec77a91e5075ec62f814232
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit e61246c419cd0655ca9dccdcd9e497440324d7b7)
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/AbstractDeclaredEffectiveStatement.java
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/AbstractSchemaEffectiveDocumentedNode.java