You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using one-indexed node numbering for so long and haven't broken a sweat.
It's just so much easier to use since even all the questions use one-indexing you don't have to worry about subtracting anything while reading input and using it.
Having to subtract 1 every time after reading input feels pointless once you get used to this.
Can we just do a quick run through of our codes for enforcing this notation? Or contrary thoughts?
The text was updated successfully, but these errors were encountered:
Although I love the 0 indexed notation and am strongly against using anything 1 indexed, I concede to your superior experience, and am willing to change that across our code. Though writing cin >> u >> v; u--, v--; is not too much of an effort, I agree that 0 indexed problems are a lot rarer on codeforces and in ICPC. Consider this and change.
I have been using one-indexed node numbering for so long and haven't broken a sweat.
It's just so much easier to use since even all the questions use one-indexing you don't have to worry about subtracting anything while reading input and using it.
Having to subtract 1 every time after reading input feels pointless once you get used to this.
Can we just do a quick run through of our codes for enforcing this notation? Or contrary thoughts?
The text was updated successfully, but these errors were encountered: