<commit_before><?xml version="1.0"?>
<package xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <metadata>
    <id>SimulatableApi</id>
    <title>Simulatable API</title>
    <version>0.0.0-build1</version>
    <authors><NAME></authors>
    <owners><NAME></owners>
    <summary>This class represents a transactional view on a file system. Actually, it represents a transactional view on an arbitrary storage medium, and this is where the Simulator comes in.</summary>
    <description>This class represents a transactional view on a file system. Actually, it represents a transactional view on an arbitrary storage medium, and this is where the Simulator comes in.

There are three ways to get a FileSystem. The first two, FileSystem.Real() and FileSystem.Simulated(), return a new view wrapped around some storage. The last, FileSystem.Clone() creates a view from another view. They share the same underlying storage, but each have their own change tracking and undo facilities.

The first thing to notice from just the above is that this is not your typical files and directories API. There is a single instance that represents the entire file system; file and directory objects are bound to a file system, and all the instances related to a single file system share consistent state.</description>
    <projectUrl>https://github.com/arlobelshee/SimulatableApi</projectUrl>
    <tags>filesystem simulator</tags><commit_msg>List Anthony as another author.<commit_after><?xml version="1.0"?>
<package xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <metadata>
    <id>SimulatableApi</id>
    <title>Simulatable API</title>
    <version>0.0.0-build1</version>
    <authors><NAME>, <NAME></authors>
    <owners><NAME></owners>
    <summary>This class represents a transactional view on a file system. Actually, it represents a transactional view on an arbitrary storage medium, and this is where the Simulator comes in.</summary>
    <description>This class represents a transactional view on a file system. Actually, it represents a transactional view on an arbitrary storage medium, and this is where the Simulator comes in.

There are three ways to get a FileSystem. The first two, FileSystem.Real() and FileSystem.Simulated(), return a new view wrapped around some storage. The last, FileSystem.Clone() creates a view from another view. They share the same underlying storage, but each have their own change tracking and undo facilities.

The first thing to notice from just the above is that this is not your typical files and directories API. There is a single instance that represents the entire file system; file and directory objects are bound to a file system, and all the instances related to a single file system share consistent state.</description>
    <projectUrl>https://github.com/arlobelshee/SimulatableApi</projectUrl>
    <tags>filesystem simulator</tags>
{'fraction_non_alphanumeric': 0.08529214237743452, 'fraction_numerical': 0.010745466756212223, 'mean_word_length': 4.717850287907869, 'pattern_counts': {'":': 0, '<': 50, '<?xml version=': 2, '>': 50, 'https://': 2, 'lorem ipsum': 0, 'www.': 4, 'xml': 6}, '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': '6234349', 'n_tokens_mistral': 783, 'n_tokens_neox': 754, 'n_words': 352}