Ryan wants to retrieve the value at the same time as removing, to reduce the double lookup. Really, the method's behavior is better described as TryGetAndRemove.
Thanks for the great suggestion! We'll consider this for a future version.
As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Thanks for the suggestion. Unfortunately, we can't do it without breaking existing applications, it's a breaking change to add an additional interface to an another interface.
Ah, actually provide the description of why the exception is thrown? Yes, that would be useful.
The exception tag should already be recognized.