Markus Schirp
Markus Schirp
Mutating private method send into local variable reads. Mutant should know the local variable scope and only emit this mutation when the local variable is in scope.
Should only be emitted when lvar is actually in scope. Can be determined statically. Adjacent to #464
These would help to detect typos in the test integration metadata.
This is a bit more complex, as we right now do not keep source locations for tests. But this should be doable without a too broad test integration API change.
- Changelog generation - Tagging - Gem building & Pushing - Link Changelog in GH tags - Other?
After deploying a co-log based logger to AWS/Lambda, I noticed that co-log would not "turn of" colors automatically when being asked to print to handles that do not point to...
It appears that `data/cloudformation/2010-05-15/service-2.json` is missing the following enum values in the `ResourceStatus` type: ``` "ROLLBACK_COMPLETE" "ROLLBACK_FAILED" "ROLLBACK_IN_PROGRESS" "UPDATE_COMPLETE_CLEANUP_IN_PROGRESS" "UPDATE_ROLLBACK_COMPLETE" "UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS" "UPDATE_ROLLBACK_FAILED" "UPDATE_ROLLBACK_IN_PROGRESS" ``` Note that all of these are...
I know this is essentially more an issue with stack/cabal/ghc. Still as this projects triggers it I'm asking here if anyone knows a workaround to get a rid of: ```...
There is lvar scope specific syntax to be emitted on certain AST constructs. It appears unparser (and rubocop) do not thread `=> expression` as an assignment at this point, miscalculating...