Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

I think what makes it so hard is that even though "Simplify the resulting mess." is a simple and common-place optimization pass done by compilers, the results are internal and transient, and can't easily be used to rewrite the source code in the new convention (0-based or 1-based). Thus, the simplification of the index math at the source code level ends up being done by hand, which is where the mistakes come in.

Alexander
– Alexander

2020-12-04 22:20:04 +00:00
Commented Dec 4, 2020 at 22:20

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »