Subnostr

yeah, performance optimization is the big cost with funcitonal languages, be it tail recursion or unfolding recursive stuff... recursion is very popular with functional languages but it has its own particular problems, i feel like the Go Authors have declined to add tail recursion to the language because the same logic is more efficiently expressed with for and switch and using concurrent channels and coroutines

Diacone Frost 1y ago

wait what? go doesn't have tail call recursion, does it?

Reply to this note

Please Login to reply.

Discussion

Diacone Frost 1y ago

sorry, I read declined as decided, lol

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

yeah they declined it, it's something you can dig out of the golangnuts mailing list from at least 5 years ago, they just don't see the point of adding this feature to the compiler because of the dramatic computation cost

Diacone Frost 1y ago

didn't know but it's type of smart decisions they tend to do.

unlike the whole module shit. that was ... hard

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

haha yeah... i refused to use modules for a whole year, they were buggy af lol

now, idk how we'd survive without it but i'm not sure they did it quite perfect, i still keep a GOPATH as a convenient way to organise all my repos

but it works!

there's some glitches here and there with dependencies sometimes though... the btcd and lnd repos notably are a shitfight of dependencies literally back to different versions of the same fucking repo, it's madness

Diacone Frost 1y ago

I too can't imagine working without modules.

but it was hard for us early adopters