{"push_id":834291682,"size":1,"distinct_size":1,"ref":"refs/heads/development","head":"2e930c9715c583ac7de4e63d6fb6f4e16c4384d5","before":"155ed38b86ab38cb5403d25d25324df5dca8c75f","commits":[{"sha":"2e930c9715c583ac7de4e63d6fb6f4e16c4384d5","author":{"email":"0a97f41250770f78133d92512cc2ef888c3c4058@umich.edu","name":"Mazin Assanie"},"message":"Some fixes for deep copy\n\n- No longer crashes Soar 9.5. (Soar expected preference for those wmes)\n- Fixed bug where Soar was generating chunks inappropriately when deep \n  copying in a substate.  Now caches level of identifier element of the \n  rhs action that called deep copy and assigns that level to the \n  identifiers created by deep-copy.\n- Note that chunking currently has significant issues with wme's that \n  were copied with deep-copy.  \n  - Tests that matched constants created by deep-copy will not be \n    variablized.  \n  - If a deep-copy is a rhs action of an instantiation that is being \n    chunked over, it will not create a chunk at all.  (This is because \n    the copied wmes are added to the results before chunking begins, \n    which become ungrounded because the condition that would have \n    provided the root variable is now a variablized rhs function.  We'd \n    need to either somehow remove those deep copied items or not \n    variablize the deep-copy rhs function.)","distinct":true,"url":"https://api.github.com/repos/SoarGroup/Soar/commits/2e930c9715c583ac7de4e63d6fb6f4e16c4384d5"}]}