Revision 04e1bfaf
ID | 04e1bfaf386bb8487c81d0dead016f19e85717cb |
Parent | 51ee2f49 |
Child | fee80e90 |
Invert nodes/instances locking order
An implementation mistake from the original design caused nodes to be
locked before instances, rather than after. This patch inverts the level
numbering, changing also the relevant unittests and the recursive
locking function starting point.
Reviewed-by: iustinp
Files
- added
- modified
- copied
- renamed
- deleted