[Bug] Array index error is not linting after upgrade to 4.1.1

[jerrykal]

@Arcanemagus This problem is not duplicated either #200 and #202, linter only not linting when array index error, here's an example:
v4.1.1

however, v4.0.0 doesn't have this problem:

[jerrykal]

@Arcanemagus Can you take a look ??

[jerrykal]

@Arcanemagus linter-gcc doesn't have this problem, maybe you can take a look.

[steelbrain]

Hi @ooJerryLeeoo
Can you show us the error message? and how it differs from the expected behavior

[jerrykal]

@steelbrain The error message in the screenshot is

error: array type 'int [1]' is not assignable

and the expected behavior is in the second screenshot.

[steelbrain]

Can you post the result of Linter: Debug command from command palette?

[jerrykal]

@steelbrain

Platform: darwin
Atom Version: 1.18.0-beta1
Linter Version: 2.1.4
All Linter Providers: 
  - clang
  - ESLint
  - JSON Lint
Matching Linter Providers: 
  - clang
Disabled Linter Providers; 
Current File scopes: 
  - *
  - source.cpp
  - meta.block.c
  - constant.numeric.c

[steelbrain]

I can debug it this weekend, busy before that sorry

[jerrykal]

Okay, I got it 👍

[jerrykal]

@steelbrain I've just found another linter error is not working too:

and the error message in the screenshot should be:

error: cannot initialize a variable of type 'int *' with an lvalue of type 'const char [5]'

[jerrykal]

@steelbrain Can you take a look ??