need documentation

[yaito3014]

I'm not sure whether it will be plain markdown or tool-generated HTML, but still some documentation will be needed.

• write meaningful README

feature list:

• allocator
  • default_init_allocator
• exec
  • atomic_queue
  • cv_queue
  • scheduler
  • worker_pool
• hash
  • hash_combine
  • hash_value_for
  • hash_ran
  • string_hash
• ranges
  • concat_view
• util
  • all_same
  • always_false
  • auto_sequence
  • exactly_once
  • find_type_index
  • forward_like
  • pack_indexing
  • specialization_of
  • array_cat
  • overloaded
  • reverse
  • to_array_of
  • to_subrange
  • to_underlying
  • wrap_as
• variant_view
• chrono
  • duration_cast
• enum_bitops
  • adaptor
  • algorithm
  • io
• inplace_vector helper
• lifetimebound
• no_unique_address
• maybe_mutex
• par_for_each
• throwt
• printt
• stack

[saki7]

Asciidoc? https://asciidoc.org/ I've heard that Boost is slowly migrating to Asciidoc, in favor of a deprecation on QuickBook.

I strongly believe that plain Markdown isn't sufficient for writing practically useful documentation. We really need to pick a decent documentation framework. I can deal with some extra work needed for learning the framework, as those efforts are essentially needed for documenting things, I guess.