prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  request
   +--examples
   +--lib
   `--tests
       +--browser
       |   `--ssl
       +--fixtures
       `--ssl
           `--ca
  ```
  
  Convert this description:
  
  async-modules is a main directory that collects 8 subdirectories. Notable ones include double-import, issue-16097, micro-ticks-parents among others.
  
  Let me break down the design for you:
  
  At the main level, 'double-import' has nothing inside.
  In the root directory, The 'issue-16097' section appears to be unused.
  At the top level, 'micro-ticks-parents' houses 5 some folders.
  In nested path 'micro-ticks-parents → case-a', Inside 'case-a', you'll find it is currently empty.
  In nested path 'micro-ticks-parents > case-b', Inside 'case-b', you'll find it is a vacant space.
  Within directory hierarchy 'micro-ticks-parents / case-c', Inside 'case-c', you'll find it is empty.
  In nested path 'micro-ticks-parents / case-d', The 'case-d' data structure sits empty.
  Within directory hierarchy 'micro-ticks-parents > case-e', The 'case-e' compartment has nothing inside.
  At the top level, The 'reexport-unknown' repository has no folders inside.
  At the main level, Inside 'runtime-performance', you'll find it lacks any subdirectories.
  At the main level, 'top-level-await' remains unused.
  At the top level, Inside 'top-level-await-without-export', you'll find it has nothing inside.
  In the root directory, 'top-level-error' has nothing inside.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "async-modules\n +--double-import\n +--issue-16097\n +--micro-ticks-parents\n |   +--case-a\n |   +--case-b\n |   +--case-c\n |   +--case-d\n |   `--case-e\n +--reexport-unknown\n +--runtime-performance\n +--top-level-await\n +--top-level-await-without-export\n `--top-level-error", "description": "async-modules is a main directory that collects 8 subdirectories. Notable ones include double-import, issue-16097, micro-ticks-parents among others.\n\nLet me break down the design for you:\n\nAt the main level, 'double-import' has nothing inside.\nIn the root directory, The 'issue-16097' section appears to be unused.\nAt the top level, 'micro-ticks-parents' houses 5 some folders.\nIn nested path 'micro-ticks-parents \u2192 case-a', Inside 'case-a', you'll find it is currently empty.\nIn nested path 'micro-ticks-parents > case-b', Inside 'case-b', you'll find it is a vacant space.\nWithin directory hierarchy 'micro-ticks-parents / case-c', Inside 'case-c', you'll find it is empty.\nIn nested path 'micro-ticks-parents / case-d', The 'case-d' data structure sits empty.\nWithin directory hierarchy 'micro-ticks-parents > case-e', The 'case-e' compartment has nothing inside.\nAt the top level, The 'reexport-unknown' repository has no folders inside.\nAt the main level, Inside 'runtime-performance', you'll find it lacks any subdirectories.\nAt the main level, 'top-level-await' remains unused.\nAt the top level, Inside 'top-level-await-without-export', you'll find it has nothing inside.\nIn the root directory, 'top-level-error' has nothing inside.\n"}