Washi

I think if we do this, including the automated `IsValueType` update, then we should also do this for `GenericInstanceTypeSignature` for consistency. If you could do that then I will merge...

Thanks a lot!

I can definitely see value in this. Perhaps as an alternative to calbacks we could also consider implementing a listener pattern for easier customization and case distinction from the user's...

Implemented in #337. This will be part of the 5.0 release.

> Which warnings are you referring to? Looking at the app veyor log, it seems there are only 4 warnings total: AppVeyor might be deceiving here, since it does not...

> What would be the best way to make that part of the continuous integration? I am not sure if it is possible directly in an appveyor.yml, as these warnings...

I am fine with using github actions, but whether we use actions or appveyor isn't going to change the fact that this test is going to require a publish on...

As far as I can see, I think to fix the warnings happening in `TypeSignature`, we need to do the following: - Remove the `ElementType.Internal` case from `TypeSignature.FromReader`, and add...

It seems like it is possible to run `dotnet publish` in AppVeyor as a custom script in e.g. the `after_test` phase, but unfortunately it won't register the warnings in the...

> any update on this? as with single file host binaries, now we can read the bundle, but if the binaries inside are r2r we cant modify then and repackage...