{'fraction_non_alphanumeric': 0.007898894154818325, 'fraction_numerical': 0.0, 'mean_word_length': 4.925233644859813, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
How to obtain Version Control support in Workspaces too

Version control deals with support for making changes. We analyze the way traditional systems handle this problem and come to the conclusion that these approaches are centered around repositories of immutable versions. As a consequence little or no support is give for controlling change outside of said repositories. We develop a model which place workspaces on an equal footing of repositories and thus we extend traditional version control support to apply to workspaces too. We show how this model was implemented and report on some of the experiences from its actual use.