Stephen Cleary
Stephen Cleary
Idea: - ~Define a simple `Disposable` and `AsyncDisposable` for the 95% use case so people don't have to remember `AnonymousDisposable` / `AnonymousAsyncDisposable`.~ Done as of 2.2.0.
- Deprecate `AnonymousDisposable` / `AnonymousAsyncDisposable`. - Change Single usage from inheritance to composition.
All changes above are in `v3.0.0-pre01`.
It can't be enforced via exceptions; it would be possible but too expensive in the async world. Enforcing by API is not a bad idea, though. Thanks for writing this...
I believe this is still an issue.
It's because of the `restore-keys` usage. Consider the [nuget example](https://github.com/actions/cache/blob/main/examples.md#c---nuget). If `packages.lock.json` contains package A, version X, then the first time this is run, there is no cache hit and...
Interesting read, but I'm not sure how well its assumptions work with the mark-and-sweep GC used by .NET. It also assumes arrays are (or can be) reallocated in place, which...
You could use PKI to encrypt the email yourself and send it as a separate field. Then it would exist (encrypted) in the PR and in your repo, but only...
If you're willing to stick to modern browsers, you can encrypt it entirely client-side with the Web Crypto API.
Just wrote up a [proof-of-concept](https://github.com/StephenClearyExamples/RsaJwk): a webpage that encrypts using WebCrypto and a C# console app that decrypts the values. However, this solution is limited to browsers that support WebCrypto,...