i am literally shaking, my hands are shaking

a story of pain

So the syntax is not the same as the one i used last time, changed it up a bit to make things easier. Here is the current version, that's working.

content, err := ioutil.ReadFile(filename)
try err or string

so the try statement expects two values

1. the error variable
2. the type of the return value (this is needed because go has this convention of returning the zero value of a type incase of an error)

so the above syntax gets expanded into the following

if err != nil {
    return make([]string, 1)[0], err
}

I have ascended beyond the mortal plain.
And golang devs you are welcome.

i really wish some of you all could run it and try it out, i am using nix to setup the environment. The readme has instructions to build it from source, if you use nix.

https://github.com/frectonz/better-go/

This is what watching Jonathan Blow clips telling you to do hard stuff does to a person. 😂

Also implemented an unwrap statement that panics when the error is not nil.

from this

unwrap err

to this

if err != nil {
    panic(err)
}

Take pride in your effort, not your talents.

"Most people die at 25... we just don't bury them until they are 70."

― Benjamin Franklin

Any thoughts on once.
I think it's a good idea but i don't know how many people will go through the hassle of running their own servers.

I am thinking of doing a demo of how i added try and unwrap to the go compiler tonight. So should i just walk through the diff explaining what each part does or should i do a live implementation of a new statement.

btw don't forget to checkout better-go for your compiler design courses, i am sure you will learn a lot 😂

Will start of at 4:10, anyone who is interested gather around until then.