Add codespell target to Makefile

Author: ClausKlein

Makefile

@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
 
 SANITIZERS = release debug msan asan usan tsan
-.PHONY: default run update check ce todo distclean clean build test all $(SANITIZERS)
+.PHONY: default run update check ce todo distclean clean codespell build test all $(SANITIZERS)
 
 COMPILER=system
 CXX_BASE=$(CXX:$(dir $(CXX))%=%)
@@ -79,6 +79,9 @@ check:
 		< $$h sed -n "/^ *# *include <Beman\//s@.*[</]Beman/\(.*\).hpp>.*@$$from \1@p"; \
 	done | tsort > /dev/null
 
+codespell:
+	codespell -L statics
+
 todo:
 	bin/mk-todo.py
 

docs/overview.md

@@ -19,7 +19,7 @@ When an asynchronous operation completes it _signals_ its completion by calling
 </details>
 <details>
 <summary>environment</summary>
-The term _enviroment_ refers to the bag of properties associated with an <code>_object_</code> by the call <code><a href=‘#get-env’>std::execution::get_env</a>(_object_)</code>. By default the environment for objects is empty (<code><a href=‘#empty-env’>std::execution::empty_env</a></code>). In particular, enviroments associated with <code><a href=‘#receiver’>receiver</a></code>s are used to provide access  to properties like the <a href=‘#get-stop-token’>stop token</a>, <a href=‘#get-scheduler’>scheduler</a>, or <a href=‘#get-allocator’>allocator</a> associated with the <code><a href=‘#receiver’>receiver</a></code>. The various properties associated with an object are accessed via <a href=‘#queries’>queries</a>.
+The term _enviroment_ refers to the bag of properties associated with an <code>_object_</code> by the call <code><a href=‘#get-env’>std::execution::get_env</a>(_object_)</code>. By default the environment for objects is empty (<code><a href=‘#empty-env’>std::execution::empty_env</a></code>). In particular, environments associated with <code><a href=‘#receiver’>receiver</a></code>s are used to provide access  to properties like the <a href=‘#get-stop-token’>stop token</a>, <a href=‘#get-scheduler’>scheduler</a>, or <a href=‘#get-allocator’>allocator</a> associated with the <code><a href=‘#receiver’>receiver</a></code>. The various properties associated with an object are accessed via <a href=‘#queries’>queries</a>.
 </details> 
 
 ## Concepts

docs/questions.md

@@ -26,7 +26,7 @@ likely observable.
 - [exec.run.loop.types] p9.2: "get_stop_token(REC(o))": REC is a receiver, any
      environment would be attached to get_env(REC(o)).
 - [exec.into.variant] p2: the sender argument to into_variant really needs to
-    have completion_signatures defined - should the constaint be sender_in
+    have completion_signatures defined - should the constraint be sender_in
     instead of sender? oh, actually, only the result of transform_sender needs
     to be a sender_in!
 - [exec.sync.wait] p4.2: what is "e"? probably apply_sender(...)
@@ -43,7 +43,7 @@ likely observable.
     supposed to work? I don't see a reason why a value completion is necessarily
     required. As is, they are not because type_idenity_t ends up being used without
     argument.
-- [exec.then] p5 seems to miss a space betweend sendr and out_sndr
+- [exec.then] p5 seems to miss a space between sendr and out_sndr
 - [exec.let] p9: Env is not defined; it is probably meant to be env_t
 - [exec.schedule.from] p6: the Rcvr in state-type shouldn't be a reference
 - [exec.when.all] uses on-stop-request without saying what it actually does.

tests/beman/execution26/stopcallback-cons.test.cpp

@@ -31,7 +31,7 @@ TEST(stopcallback_cons) {
     // done is to verify that construction and destruction works even if the
     // callback is the only owner of the state.
     // - Given a stop_callback constructed from an engaged stop_token.
-    // - When the corresponding stop_source and stop_token are destoryed.
+    // - When the corresponding stop_source and stop_token are destroyed.
     // - Then the callback can still be destroyed without issues.
 
     auto                                source = ::std::make_unique<::test_std::stop_source>();

tests/beman/execution26/stopsource-mem.test.cpp

@@ -54,7 +54,7 @@ auto test_stopsource_stop_possible() -> void {
     //  - Given an engaged and a disengaged stop sources.
     //  - When using stop_possible()
     //  - Then the result is true for the engaged stop source (both
-    //    before request_stop() was calle and after) while
+    //    before request_stop() was called and after) while
     //    the result is false for the disengaged stop source.
     // Reference: [stopsource.mem] p3