<commit_before>internal quoting in expressions can't be "" needs to be sanatised to '' (is this ok?)
 NO: root[prev.program][prev.pc] == ">" &&

might want to coerce for methods like .contains()

overly complex generated expressions, need more optimizing

change mail_example to mail (in documentation too)

Comments in long expressions, is there a way to do this?

bug (not in blaze) in low level rules, using a number as a index does not work (does not cast to string for child)<commit_msg>suggestion for moving from "write" to "validate" for heirarchical expressions<commit_after>internal quoting in expressions can't be "" needs to be sanatised to '' (is this ok?)
 NO: root[prev.program][prev.pc] == ">" &&

might want to coerce for methods like .contains()

overly complex generated expressions, need more optimizing

change mail_example to mail (in documentation too)

Comments in long expressions, is there a way to do this?

bug (not in blaze) in low level rules, using a number as a index does not work (does not cast to string for child)

Is using a validate instead of write better for inheritance across $whildchild relations? Waht about if a user sets a child to null.
Is there a way to prevent things being nulled?
{'fraction_non_alphanumeric': 0.06834825061025224, 'fraction_numerical': 0.0, 'mean_word_length': 4.694444444444445, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, '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': '2902437', 'n_tokens_mistral': 335, 'n_tokens_neox': 318, 'n_words': 186}