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

Agreed Syntax #1

Open
b3nten opened this issue Aug 12, 2022 · 8 comments
Open

Agreed Syntax #1

b3nten opened this issue Aug 12, 2022 · 8 comments

Comments

@b3nten
Copy link
Member

b3nten commented Aug 12, 2022

Lets update this issue with finalized (for now) syntax replacements.

I don't want to make this a discussion, we can keep that on discord for now. But this is a good place to record what we decide on.
For now we have:

// Main keywords
function === finna
true === nocap
false === cap
error === oof
throw === yikes
const === facts
return === yeet
delete === smash
new === fresh

// Flow Control
if === fr
else === lowkey
else if === fr lowkey
break === ded
try === bet

// Promises
Promise() === Gotchu()
reject === sheesh
resolve === bussin
then === bless
catch === sus
finally === ong

// Types
:hash: === number
:pencil2: === string

// Other shit that I can't be fucked to categorise
setTimeout() === holUp()
os.exit() === kms
console.log("") === slide.dm("")
Array === Fam
Object === Chad
Map === Gigachad

// TODO: *Maybe* think about OOP
class === boomer
@critical
Copy link

Thoughts on lowkey for else?

@stoykotolev
Copy link

Why not use facts === true

@b3nten
Copy link
Member Author

b3nten commented Aug 12, 2022

Is there something that makes sense as an anti-facts?

@stoykotolev
Copy link

fake news

@b3nten
Copy link
Member Author

b3nten commented Aug 12, 2022

I think we should avoid keywords being two separate words, might make it difficult to write a compiler

@critical
Copy link

@stoykotolev made a good suggestion to add this to Git to maintain and reference the original shitpost that started this entire thing

finna doSomething() {
  bet {
    // try
  } sus e {
    // catch
  } ong {
    // finally
  }
}

We should probably keep this as our try/catch/finally block. The original image I posted doesn't have the bet keyword but I feel like it fits for this usecase. Thoughts?

@henriqgoncalvs
Copy link

henriqgoncalvs commented Aug 12, 2022

more random ideas

Best practice for this lang is going to be having all the comments be //IYKYK

.Gru file extension?

are observers/event listeners stans?

document to dox maybe?

array = fam, class = boomer

object === chad, map === gigachad

null = nah

cap/nocap is true/false I think

index 69 start

the main branch is goat, the dev is horny

@kubre
Copy link

kubre commented Aug 12, 2022

Return = gg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants