GitHub Super Linter: one linter to rule them all

Re:GitHub Super Linter: one linter to rule them all by philsnow on Thursday June 18, 2020 @10:56PM (#23570518)

That was maybe not a great example, pick any language change where a new keyword was introduced that wasn't previously a keyword or reserved word.

I tried to make an example with `with`, because that was introduced between 2.4 and 2.5 IIRC, and 2.4 and 2.5 aren't nearly as far apart as 2.* and 3.*, but I didn't find an easy way to install a 2.4 python (it didn't compile in pyenv on my mac, and I looked at a couple docker images before giving up).

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by Dylan16807 on Friday June 19, 2020 @01:16AM (#23571213)

But you're describing a benefit of storing an AST. Instead of the code suddenly changing meaning, you have an AST that says what the meaning should be.

The worst case is that you export it with the old version of the converter, and then the code changes meaning. You have silent corruption. But if you stored raw text this would always happen.

The good case is that you export it with the new version of the converter. It will notice that a variable name matches a keyword, and alert you to fix it.

[ Parent | on HN ]