INDAPlus21 / INDAPlus21/azeezd-assembly

Pass

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

**Very well done Azeez!**

Nice pic!

You have a great error coverage and I like your compact thinking. Your applications are rarely partitioned over a confusing amount of functions and structures.

The only concern I've found is `tokens`. It forces the compiler to print error messages with a trace based on instruction index. Try tracking instruction #123 in a file with frequent empty lines.
```rust
let tokens : Vec = inst
.split_whitespace()
.map(|_token| _token.to_string())
.collect();
```

Otherwise, I'm all for it! Thank you for you effort!

Can be found in Datas Sångbok:
```
When I find my code in tons of trouble,
Friends and colleagues come to me,
Speaking words of wisdom:
"Write in C."

As the deadline fast approaches,
And bugs are all that I can see,
Somewhere, someone whispers"
"Write in C."

Write in C, write in C,
Write in C, write in C.
LISP is dead and buried,
Write in C.

I used to write a lot of FORTRAN,
for science it worked flawlessly.
Try using it for graphics!
Write in C.

If you've just spent nearly 30 hours
Debugging some assembly,
Soon you will be glad to
Write in C.

Write in C, write in C,
Write In C, yeah, write in C.
Only wimps use BASIC.
Write in C.

Write in C, write in C,
Write in C, oh, write in C.
Pascal won't quite cut it.
Write in C.

Guitar Solo

Write in C, write in C,
Write in C, yeah, write in C.
Don't even mention COBOL.
Write in C.

And when the screen is fuzzy,
And the edior is bugging me.
I'm sick of ones and zeroes.
Write in C.

A thousand people people swear that T.P.
Seven is the one for me.
I hate the word PROCEDURE,
Write in C.

Write in C, write in C,
Write in C, yeah, write in C.
PL1 is 80's,
Write in C.

Write in C, write in C,
Write in C, yeah, write in C.
The government loves ADA,
Write in C.
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Search the compiler for the `tokens` collection shown in the issue and inspect how instruction indices are used in error traces. Reproduce the diagnostic on a file with frequent empty lines and compare the reported location with the source. Done means error traces identify the correct source position rather than only an instruction index.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.