<commit_before>install Rust?
install Swift?
install Visual.BASIC (for <NAME>)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Each language should have a (docker running) test that confirms it
  o) starts at red
  o) if the _named_file_ is s/6*9/6*7/ it becomes a green
     where the named_file is part of the test data
  o) adding gibberish gives amber
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
admin_scripts/check_language_manifest.rb
  should become part of the main test suite.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
admin_scripts should also have basic sanity tests, eg that
  they run without require errors.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
cyberdojo/exercises/ folder could be beefed up to match
the cyberdojo/languages folder and has a manifest.json
file and can have visible_filenames.
It's entirely possible someone in education might want to
setup several specific start-point exercises for the same
language.
The problem with this though is that it would mean various
exercises being offered which were only appropriate for
a specific language. Perhaps allow each language to have
an exercises subfolder? At the moment the language manifest
specifies the bare bones source files for the code and test
file. These need to somehow be separated out so that they are
not included if a "custom" exercise is used.
How about having a language appear twice. Once as it currently
is with no exercises folder underneath the languages/*/ folder
and its manifest names and used the code and test files.
And again with an exercises/ folder underneath the
languages/*/ folder whose manifest does not name any code/test
files - they come from the custom exercises.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<commit_msg>deleted done things from notes file<commit_after>install Rust?
install Swift?
install Visual.BASIC (for <NAME>)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Each language should have a (docker running) test that confirms it
  o) starts at red
  o) if the _named_file_ is s/6*9/6*7/ it becomes a green
     where the named_file is part of the test data
  o) adding gibberish gives amber
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
admin_scripts should have basic sanity tests, eg that
  they run without require errors.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
cyberdojo/exercises/ folder could be beefed up to match
the cyberdojo/languages folder and has a manifest.json
file and can have visible_filenames.
It's entirely possible someone in education might want to
setup several specific start-point exercises for the same
language.
The problem with this though is that it would mean various
exercises being offered which were only appropriate for
a specific language. Perhaps allow each language to have
an exercises subfolder? At the moment the language manifest
specifies the bare bones source files for the code and test
file. These need to somehow be separated out so that they are
not included if a "custom" exercise is used.
How about having a language appear twice. Once as it currently
is with no exercises folder underneath the languages/*/ folder
and its manifest names and used the code and test files.
And again with an exercises/ folder underneath the
languages/*/ folder whose manifest does not name any code/test
files - they come from the custom exercises.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
{'fraction_non_alphanumeric': 0.12312312312312312, 'fraction_numerical': 0.002184002184002184, 'mean_word_length': 1.942971887550201, 'pattern_counts': {'":': 0, '<': 5, '<?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': 44, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5251094', 'n_tokens_mistral': 1102, 'n_tokens_neox': 1083, 'n_words': 457}