Hacker News Reader

Comment by grajaganDev | Hacker News Reader

Const whenever possible.

I'm with you, const whenever possible. Fewer things to reason about and chase down while diagnosing issues or debugging. I also thought this was the default for a majority of developers.

Right, the hope is to find bugs early.

This is what I would call const correctness, because it is correct.

Funny, that's not my preferred one nor the teams

Should it be mutable or not? Seems reasonable to answer up front by choosing const or let.

What are other considerations?

After thinking about it a bit more, I think I am actually on your side. I previously claimed to be on "Const when things should never locally change".

But thinking through the example

function expectedRevenuePerAttempt() {

  (const/let) successRate = success / attempt;

  return successRate * revenuePerSuccess

}

I would prefer to use const there.

Reply on news.ycombinator.com