Please sign in to comment.
Error-Trace shows bogus values - #372
- Part of the underlying Tree implementation is relying on the item's hashcode, so our purposing of the hash calculations to make it easy to filter all TLCVariables based on a single proto-variable instance was resulting in the data for one instance of TLCVariable being shown for all of the same name/is-explorer couplet value. Have discontinued overriding hashcode for our filtering purposes. #372 [Bug][Regression][Toolbox]
- Loading branch information...
Showing with 16 additions and 27 deletions.