"there are only pioneers"

So apparently the go compiler does type checking twice, it first type checks the parsed syntax tree then it also type checks the AST.

i can't believe people are agreeing with this comment i made on a wonder soul post

"paper production machine"

https://youtu.be/LKiBlGDfRU8

i think my love language is making progress. nothing makes me feel better, love myself, and be proud like a fucking progress

accelerare profectum! ✊🏾

You are not an open source enthusiast you just like free stuff.

a story in 10 commits, i am literally at the last step 😭

If @yohan_nes 's arc has thought me anything it's that becoming skilled in android development inevitably leads to starting to learn ios development. 😂

The most linked to article in Wikipedia is the article for the United States.

https://youtu.be/JheGL6uSF-4

This thing is so close to working but the typecheck is failing, after i transform the try statement to a regular if statement.

from this

try c or string = ioutil.ReadFile(filename)

to this

content, err := ioutil.ReadFile(filename)
if err != nil {
    var content string
    return content, err
}

it's expecting content to be SLICE-[]byte but the function returns a []byte.

This is actually a good way to test people. How people react to this is kind of telling.

Github for <insert white collar job>.

Any go devs here who know what might be going wrong with this.

Why am I spending all this effort to fix this overrated garbage lang. They mention that the current go compiler code was auto translated to go from the original c version and it shows, the codebase starting from the directory structure is just disappointing.

From all the compiler codebases I have seen I think python was the only well structured one.

cloudflare just keeps winning and it's all open source.

https://blog.cloudflare.com/javascript-native-rpc

Those who can DO
Those who can't DEI

debugging at the disco