-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
!! / !bang? #34
Comments
Would you two be open to me taking a stab at this one? |
iirc this is hard / not really feasible since every message is dispatched independently and asynchronously |
I was poking around and the Lines 113 to 116 in 50341c3
How to handle keeping message permissions from being skipped, that all commands are stripped of extra bangs, and the command pattern doesn't presently match Line 144 in 50341c3
Line 18 in 50341c3
(either way, neat implementation and I learned a few things digging through it which was my primary goal!) |
the aliasing system is for command names and probably wouldn't work or help for command values -- it's also meant to be ~immutable after process startup |
The text was updated successfully, but these errors were encountered: