Skip to content
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

Open
tempewda opened this issue Oct 7, 2022 · 6 comments
Open

rules to UwUfwicatwion? #38

tempewda opened this issue Oct 7, 2022 · 6 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@tempewda
Copy link
Contributor

tempewda commented Oct 7, 2022

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

@LordUbuntu
Copy link
Contributor

LordUbuntu commented Oct 9, 2022

I've honestly been thinking about this idea for a while.

Uwufication has some de-facto standard pattern that it already follows:

  • any u is substituted with an uwu
  • any l and r is substituted with a w (we don't take L's here)
  • not sure about owo, we might need to clarify where that applies..

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 wintew?

Another rule I thought might be in line with this might be requiring that every function name must start (or maybe end) with an owo, like a function named add must be named owoadd (or maybe addowo).

@tempewda
Copy link
Contributor Author

tempewda commented Oct 9, 2022

yes i love the idea of a linter for pythOwO

as for owo , u can add it to nouns that were exempted from the previous 2 mentioned rules, i.e., they don't have any u, l or r. Such as math, so in this case, owo just gets added to its end

@LordUbuntu
Copy link
Contributor

Bet. I'll start work on a linter and demo program next friday!

@virejdasani virejdasani added help wanted Extra attention is needed good first issue Good for newcomers labels Oct 10, 2022
@LordUbuntu
Copy link
Contributor

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 owo).

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.

@ironkayman
Copy link

ironkayman commented Nov 26, 2022

There is an article describing something like this, page 206, "Optimal degeneracy through OwO based variable names"

@Almas-Ali
Copy link

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.

@tempewda @LordUbuntu @ironkayman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants