-
Notifications
You must be signed in to change notification settings - Fork 46
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
rules to UwUfwicatwion? #38
Comments
I've honestly been thinking about this idea for a while. Uwufication has some de-facto standard pattern that it already follows:
This could be enforced with a linter, formatter, or the language itself to ensure UwU compliancy. Maybe we should start a project on that? A Another rule I thought might be in line with this might be requiring that every function name must start (or maybe end) with an |
yes i love the idea of a linter for pythOwO as for |
Bet. I'll start work on a linter and demo program next friday! |
So writing a BrainFuck interpreter for a demo turned out to be beyond the language's capacity within the time I had to work on it today. I also discovered the hard way that a linter is not very easy, even harder when determining what is and is not a noun. I did however manage with the time I had left to write an example function in pythOwO which takes a character and returns a string that substitutes it, which accomplished some of the patterns discussed here (everything but In the future this could be used towards implementing a full-blown linter and bootstrap compiler, but for the moment the language limitations prevent that. |
There is an article describing something like this, page 206, "Optimal degeneracy through OwO based variable names" |
Hey, you can tryout this project https://github.com/radon-project/radon because this projects are not maintaining. We will move a language together. It's very exciting. We have implement class feature in our project. Also standard library and third party imports. See you there. |
what if we define some rules so that we can identify when to use "uwu" and "w" during uwufwicatwion?
so suppose we have 3 words, number, please, math
they get uwufied as:
number -> nuwumber
please -> pwease
math -> mathowo
(source: calcuwulator.pyowo)
setting some rules would help future contributors during uwufwicatwion, n will prevent over/under uwufwicatwion at times
:3
The text was updated successfully, but these errors were encountered: