<commit_before># `new` agnostic

Even your function is called or not using `new` keyword, you can force to have the same behavior in both cases:
<commit_msg>Update new.md<commit_after># `new` agnostic

You can force an `Object` constructor to return an instance of the `Object` even when the `new` keyword hasn't been used:

{'fraction_non_alphanumeric': 0.07716049382716049, 'fraction_numerical': 0.0, 'mean_word_length': 5.132075471698113, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, '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}}
{'dir': 'git-commits-cleaned', 'id': '5851628', 'n_tokens_mistral': 95, 'n_tokens_neox': 93, 'n_words': 49}