Skip to content

Instantly share code, notes, and snippets.

@aryairani
Created March 23, 2020 21:58
Show Gist options
  • Save aryairani/df615bf8076ff1b1ef2b7726db0e74c7 to your computer and use it in GitHub Desktop.
Save aryairani/df615bf8076ff1b1ef2b7726db0e74c7 to your computer and use it in GitHub Desktop.

We were seeing an issue where (it seemed) that every namespace that was visited during a propagate would get a new history node, even when it didn't contain any dependents.

Example:

a = "a term"
X.foo = "a namespace"
.> add

  ⍟ I've added these definitions:
  
    X.foo : ##Text
    a     : ##Text

Here is an update which should not affect X:

a = "an update"
.> update

  ⍟ I've updated these names to your new definition:
  
    a : ##Text

As of the time of this writing, the history for X should be a single node, #4eeuo5bsfr;

.> history X

  Note: The most recent namespace hash is immediately below this
        message.
  
  ⊙ #7nl6ppokhg
  
    
  
  ⊙ #4eeuo5bsfr
  
    + Adds / updates:
    
      foo
  
  □ #7asfbtqmoj (start of history)

however, as of release/M1i, we see a extra, seemingly node (#7nl6ppokhg) appear:

.> history #7nl6ppokhg

  Note: The most recent namespace hash is immediately below this
        message.
  
  ⊙ #7nl6ppokhg
  
    
  
  ⊙ #4eeuo5bsfr
  
    + Adds / updates:
    
      foo
  
  □ #7asfbtqmoj (start of history)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment