Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Keyed list entry builder should cross-reference keys and their constituents

Description

Given the simple model:

generated entry lifecycle is a bit weird, as it is possible to create a Lst which has a mis-matching key() and getKey(). This is because key() is a separate "property", as that allows sharing a single object across copies - but key constituents are not cross-referenced so that the key is reset when a conflicting leaf is stored.

Design and implement an efficient way of cross-referencing the two, so that users do not get surprises.

Activity

Show:

Robert Varga October 10, 2018 at 6:00 PM
Edited

Current codegen prefers the values captured in the key, i.e. Builder fields for them are not consulted if the key is present.

Details

Assignee

Reporter

Components

Priority

Created October 10, 2018 at 4:39 PM
Updated July 5, 2024 at 7:08 PM
Configure
Loading...