Update cf-1808B.mdx

[dikshitudbhav]

Place an "x" in the corresponding checkbox if it is done or does not apply to this pull request.

• [ x] I have tested my code.
• [ x] I have added my solution according to the steps here.
• [ x] I have followed the code conventions mentioned here.
  • I understand that if it is clear that I have not attempted to follow these conventions, my PR will be closed.
  • If changes are requested, I will re-request a review after addressing them.
• I have linked this PR to any issues that it closes.

The given solution is unnecessarily complicated.

[eysbutno]

Is your solution different than the existing solution? Because, at least at a glance, they appear to be equivalent.

If they are essentially the same, then I think it would be more useful to improve the current solution (which is valid).

[apex-kevin-s]

reviewing from my corpo account LOOOL

[apex-kevin-s]

honestly i'd prefer you use cin and cout

[eysbutno]

is there any particular reason for replacing the existing solution code? since they appear identical in terms of functionality, and the original code is closer to the usual standards for guide code (though your code is more concise)

I do think that rewriting the current explanation is worthwhile though

[dikshitudbhav]

is there any particular reason for replacing the existing solution code? since they appear identical in terms of functionality, and the original code is closer to the usual standards for guide code (though your code is more concise)

The previous code used a prefix sum to calculate suffix differences, which is not required when contribution of each element could be found directly.

[eysbutno]

is there any particular reason for replacing the existing solution code? since they appear identical in terms of functionality, and the original code is closer to the usual standards for guide code (though your code is more concise)

The previous code used a prefix sum to calculate suffix differences, which is not required when contribution of each element could be found directly.

good point, it'd be nice if you kept the code style the same tho (e.g. use cin/cout over scanf/printf, spacing, etc)

explanation looks good