b6980f3

Branches > main > b6980f3 > files / resources / favicon.txt

Remove redundant comments

Grahp, 2026-07-10

Commit: b6980f349deb6291c19f8464608326d8bd97f785
Parent: e3dbdf6

1 changed file:

src/net/bowmap/message_application.clj modified (view file)

@@ -1,3 +1,4 @@+; TODO move, idk to where :p (ns net.bowmap.message-application   (:require    [clojure.spec.alpha :as s]@@ -13,17 +14,6 @@ (s/def ::messages (s/coll-of ::msg/message :type vector?)) (s/def ::response (s/keys :opt [::client/client ::messages])) -; TODO-; I do think having these processes/timeouts/whatever be data with a deadline and just run the things by deadline order is better-; Right now they're scheduled and then you don't even know where they are and have no way to access them or associate them with-; a client...--; Can also shell out to the server and just send a fact in that'll get handled, asynchronously I guess?-; Because this only deals in messages and new client state returned right now.--; TODO rename :p-; Just return effects instead?-; Handle them at the client level (defmulti handle-message   "'Applies' a message to a client state. Returns the new client state, as well    as the effects that should occur from this message (see the spec)."