You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 3, 2018. It is now read-only.
There's a lot of inter-calls on baseVCSSource, and its derived types, as they exist today. These types have seen...uh, let's call it "organic growth," and are turning into spaghetti. The main problems are:
Pretty much all of the methods take out locks - both the "porcelain" and the "plumbing." As a result, porcelain often ends up reimplementing plumbing, as calling the plumbing would deadlock.
There's a proliferation of individual bits, flags, bools, etc., which represent separate but interrelated states. These need to be consolidated and managed better.
Basically, I got lazy and started focusing on actions, rather than retaining the overall-consistent-state approach, and let things fall into disrepair.
The text was updated successfully, but these errors were encountered:
There's a lot of inter-calls on
baseVCSSource
, and its derived types, as they exist today. These types have seen...uh, let's call it "organic growth," and are turning into spaghetti. The main problems are:Basically, I got lazy and started focusing on actions, rather than retaining the overall-consistent-state approach, and let things fall into disrepair.
The text was updated successfully, but these errors were encountered: