Do not use singleton ImmutableMap for datatree/schematree 97/87297/1
authorRobert Varga <robert.varga@pantheon.tech>
Wed, 29 Jan 2020 00:39:50 +0000 (01:39 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Thu, 30 Jan 2020 10:44:17 +0000 (11:44 +0100)
commit9ff7a7d60f19f93436f40b7a1676b5edb4bb7de5
tree48efe3f129bbeb5f26da72f0a7bca405aa1cb9c0
parent5a96be8c33b2df7b5c85599890d325ba48d9bb7c
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)
(cherry picked from commit bd432e731100aa299d5564f930efcb91e0ee57e9)
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