undefined | Better HN

0 pointsdullgiulio5y ago0 comments

Go does not have exception (exactly because of this problem.)

For passing information, you use channels, which can pass more than one value back to the caller.

The big thing is not running tasks in the background but the tight integration of channels and runtime scheduler that allows having an invisible event loop on top of what is synchronous programming.

0 comments

tsimionescu5y ago

I think there are many reasons why Go doesn't use exceptions, though this is possibly one of them.

Channels are nice, but they are not that hard to replicate in other languages (probably less efficiently). They have their uses, but they can't completely supplant shared memory or async/await - all 3 are nice to have in different situations.

j / k navigate · click thread line to collapse

0 pointsdullgiulio5y ago0 comments

Go does not have exception (exactly because of this problem.)

For passing information, you use channels, which can pass more than one value back to the caller.

The big thing is not running tasks in the background but the tight integration of channels and runtime scheduler that allows having an invisible event loop on top of what is synchronous programming.

0 comments

tsimionescu5y ago

I think there are many reasons why Go doesn't use exceptions, though this is possibly one of them.

j / k navigate · click thread line to collapse