Steve Gilham
Steve Gilham
Here's an experimental build that attempts to identify and fix the defective constant definitions [altcover.8.3.702-github-pre.nupkg.zip](https://github.com/SteveGilham/altcover/files/9541063/altcover.8.3.702-github-pre.nupkg.zip) It will log as a warning any such constant giving its name and the method...
That's very interesting, as the type `IList` is not a primitive (integer, bool, or such), but one that does have a legitimate null value. The `MoveNext()` method is of course...
That's even simpler than I'd expected. Thank you for that.
Cecil issue 873 raised; and PR submitted. For the moment, though, I shall retain the experimental changes, awaiting a new release of that library.
[AltCover 8.3.839 release](https://www.nuget.org/packages/altcover/8.3.839#release-body-tab) contains this fix but with the messages directed to the Verbose rather than Warn output channel.
This is using SDK 6.0.401 and FSharp.Core 6.0.6 -- the absolute latest at time of writing.
Using fantomas, the tool itself indicates the code will become invalid  When forced, this is the sole difference in the file ([github at the 'before' state](https://github.com/SteveGilham/altcover/blob/3ba6c162db9c30c42d834165e33ccdfd06e8032a/AltCover.Engine/Main.fs))  but then running fantomas over that code gives  which this time gives a useful error message...
The above was with 5.0.0 installed; having upgraded to 5.0.2,  nothing else changes. FWIW, configuration file used [is here](https://github.com/SteveGilham/altcover/blob/1c4e88dda86fe119b11e114b107ea9ba438c31f3/.editorconfig); the first 3 lines are the only ones...
Experimenting with `.editorconfig`, the significant factor is setting `indent_size=2`; my intuition is that the block is detected as being indented one indent size, and that is assumed sufficient not to...