i read that thread, and TBH it looks like the issue was indeed rejected on pragmatic reasons. Coming from a language that is slowly but surely trending to an "

i read that thread, and TBH it looks like the issue was indeed rejected on pragmatic reasons. Coming from a language that is slowly but surely trending to an "everything and the kitchen sink" PL (aka swift), believe me, i appreciate A LOT the care with which go team makes sure any new feature composes perfectly with the existing state of the language and doesn't add too much complexity.