So you want them to completely break every pre-existing Go program, for no pract... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		rstat1 on Aug 14, 2023 \| parent \| context \| favorite \| on: Backward Compatibility, Go 1.21, and Go 2 So you want them to completely break every pre-existing Go program, for no practical benefit? That seems dumb.

AtNightWeCode on Aug 14, 2023 [–]

No. It would only be a flag to allow obsolete Go code in practice I guess.

EDIT: C++ did not break C. The people managing Go have full understanding of dependencies even though they made breaking changes.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact