{'fraction_non_alphanumeric': 0.02111324376199616, 'fraction_numerical': 0.0, 'mean_word_length': 5.289156626506024, '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}}
Tools for a successful refactoring

Although refactoring tools have been integrated into numerous development environments over the past ten years, we have seen little variation in the human interfaces to refactoring tools -- when a refactoring fails, most tools present a textual error message. Existing interfaces can cause programmers to refactor slowly, conservatively, and in an error-prone manner. In this demonstration, we will show how our tools can help programmers overcome barriers to a successful refactoring.