<commit_before>* shared stack usage scenario (chinlish ? 😂)
In fact, the use of such a data structure, usually when the two stack space requirements have the opposite relationship.
Like buying and selling stocks, when you buy, there must be somebody who is doing the sell operation. Some people make money,
it must be someone to lose money. So that the use of two stacks of shared space storage method has a relatively large significance.
Otherwise the two stacks are constantly growing, it will soon overflow.
<commit_msg>update readme.org<commit_after>* shared stack usage scenario 🙃
  In fact, the use of such a data structure, usually when the two stack space requirements have the opposite relationship.
  Like buying and selling stocks, when you buy, there must be somebody who is doing the sell operation. Some people make money,
  it must be someone to lose money. So that the use of two stacks of shared space storage method has a relatively large significance.
  Otherwise the two stacks are constantly growing, it will soon overflow.

{'fraction_non_alphanumeric': 0.03444976076555024, 'fraction_numerical': 0.0, 'mean_word_length': 4.534391534391534, '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': '6881644', 'n_tokens_mistral': 236, 'n_tokens_neox': 230, 'n_words': 168}