Add the most FIRE keywords no cap (+echo server!) #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Shit's fire 🔥🔥 |
ofekashery
approved these changes
Dec 19, 2024
|
Slay |
|
Why not |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I swear this is lit as hell. New keywords mapped:
outside ->
asynctouch grass ->
awaitbuilt like ->
=fr ->
iscap ->
notlink up ->
andpeep ->
readdrop ->
writeidk lowkey ->
or.I also implemented an entire echo-server natively in
pygyatusing the new terms. The whole process was lots of fun so I hope this will be merged quick.The echo server implementation is added to
testcases/.