aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
author zaaarf <zaaarf@proton.me>2023-08-22 11:09:27 +0200
committer zaaarf <zaaarf@proton.me>2023-08-22 11:09:27 +0200
commitbfc4753e6674cc74485e2433f80214f3ff21b70b (patch)
tree19a5de289e6556b23df733924eff23a240e29d9b /README.md
parentd48726c80f0edb159f8df80d10267ad26a3efe03 (diff)
chore: separated processor and api
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 267ed9c..5461cf6 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ Suppose that you have a simple event system, with annotated listeners receiving
That works, of course, but it's not that fast. Ah, if only you knew in advance, such as at compile time, who's going to get called with what... oh, wait, you do.
-GEB is just a basic event bus in itself; the actual magician is the processor, who writes into each event direct calls to all subscribers, to take as little time as possible.
+GEB is just a basic event bus in itself; the actual magician is the [processor](https://github.com/zaaarf/geb-processor), who writes into each event direct calls to all subscribers, to take as little time as possible.
## What's with the name?
"GEB Bus" kind of sounds like "Jeb Bush" and I think it's very funny. Please clap. \ No newline at end of file