foresterre / foresterre/parameterized
nightly: position of error pointer in ui different than current stable (1.39)
- Dominant language
- Rust
- Stars
- 27
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
**test tests/fail/square_brackets.rs** ... mismatch
```
EXPECTED:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: expected curly braces
--> $DIR/square_brackets.rs:3:21
|
3 | #[parameterized(v = [1, 2, 3])]
| ^^^^^^^^^
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
ACTUAL OUTPUT:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: expected curly braces
--> $DIR/square_brackets.rs:3:21
|
3 | #[parameterized(v = [1, 2, 3])]
| ^
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with tests/fail/square_brackets.rs and compare the expected diagnostic with the actual output shown in the issue. Determine which error-pointer position should be retained for the nightly versus stable compiler, then update the test expectation so the test matches the intended output and passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100