Markus Schirp

@akimd This is fixed in #366 but #366 is not release ready yet, its a big change on how unparser does dynamic string literals and needs more testing. ``` $...

@marcandre Its very likely all of these are fixed by #366 (not merged at the time of post). It changes the dstr node unparsing to an exhaustive search of all...

@joris974 I'm working on a bigger refactoring that will make stratosphere generate one library per AWS service, and during this process also regenerate the library. The current generator is not...

This was addressed via #207 (unreleased) and a major breaking API change I've yet to better document.

> This is also an unsafe optimization, as it is hard to achieve 100% test coverage. What exactly would you measure for using that 100% as a target? All statements...

> What we could consider instead is making it a scheduled job that runs periodically which Github Actions seems to support. Happy to set this up. But: Mutant will soon...

Interesting one. So I do not think #1337 will fix it, mutant first has to discover the changed lines relative to the provided git reference before than using the AST...

> What it does allow is setting a custom diff tool via env var though and this has let me fix my workflow. I think mutant could set the external...

@swistak35 I've got a private POC but not a full tool for SQL mutations. I need to find time during a sabattical to work on it. Note it would be...

BTW I had a reason to hadn roll my own runtime, mostly as I needed better exception handling control, especially being able to let the runtime crash and NOT re-use...