Enrico Massone

@TylerBrinkley thanks for the contibution. **I noticed that your code actually does not raise any warning inside of visual studio 2019, even with nullable reference types enabled**. The **only** way...

> I think the single `string` parameter [overload](https://github.com/JamesNK/Newtonsoft.Json/blob/master/Src/Newtonsoft.Json/JsonConvert.cs#L718) just got missed when the library was annotated. > > I'd imagine with custom converters you could conceivably return `null` from a...

> @TylerBrinkley do you now actually why `JsonConvert.DeserializeObject("null")` returns null? I think `"null"` is not a correct JSON regarding to JSON format docs. So, I think more sense has the...

Hello @b-twis I agree with you. A few months ago I proposed a pull request already including the idea of a `TryGetValueAsync` This is my pull request: https://github.com/alastairtree/LazyCache/pull/157 If you...

> Exactly as you describe - if you allow someone to cache `null`, they cannot determine when doing a Get if the item was removed from the cache or if...

Unfortunately the whole concept of null reference is deeply rooted into the language. I have seen various examples of functional libraries attempting (among the other things) to eradicate the null...

> Yeah that all makes a lot of sense to me and would tidy things up - I would accept a PR based on those changes with supporting unit tests....

Hi @alastairtree did you take a chance to evaluate my pull request ?

Using the IAppCache.TryGetValueAsync method is quite convoluted. Consider this example: ``` var cache = new CachingService(); const string key = "my-key"; await cache.GetOrAddAsync(key, async () => { await Task.Delay(100); return...