<commit_before>\chapter{Evaluation}

  \section{Original Semantics}
  
  \section{Impurity}
  
  \section{Demo Applications}
  
  \section{Limitations}<commit_msg>Plan evalutation<commit_after>\chapter{Evaluation}
  
  \section{Original Semantics}
    % With massive restrictions it works
    % Removes functionality
  
  \section{Impurity}
    % Behaviour functions can read external sources
    % As reading is done in real time its kind of ok
    % Behaviour functions can cause side effects - not good
    % Must assume programmers know what they are doing
    % Good documentation is needed
  
  \section{Demo Applications}
    % Demo applications provide test of development process
    % Music application easy to develop logic (very intuitive)
    % Needed abstraction for Song but produces resuable component
    % Password application easy to develop
  
  \section{Limitations}
    % No predicate function
    % Removes ability to evaluate Behaviours at any time
{'fraction_non_alphanumeric': 0.053497942386831275, 'fraction_numerical': 0.0, 'mean_word_length': 3.589622641509434, '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': '6863148', 'n_tokens_mistral': 262, 'n_tokens_neox': 240, 'n_words': 97}