That wasn't exactly what I meant. What I meant was - as of right now they are di... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

JulianMorrison on Feb 4, 2022 | parent | context | favorite | on: What I'd like to see in Go 2.0

That wasn't exactly what I meant. What I meant was

- as of right now they are different, and clearly distinct, and it's actually important to unlearn thinking of a const as a var, because they don't do the same thing in practical terms

- that proposal would muddy the distinction.

tapirl on Feb 4, 2022 [–]

Yes, they are different, const values doesn't allocated in memory NOW. But who cares? Most gophers just think const values are immutable values.

I mean we could let some const values allocated in memory.

JulianMorrison on Feb 4, 2022 | [–]

Thankfully the people who make Go do care about conceptual muddles.

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