{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/Logging/issues/454","repository_url":"https://api.github.com/repos/aspnet/Logging","labels_url":"https://api.github.com/repos/aspnet/Logging/issues/454/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Logging/issues/454/comments","events_url":"https://api.github.com/repos/aspnet/Logging/issues/454/events","html_url":"https://github.com/aspnet/Logging/issues/454","id":161564179,"number":454,"title":"BeginScope<TState>(TState state) feels like a good but cancelled idea","user":{"login":"sandorfr","id":2660262,"avatar_url":"https://avatars.githubusercontent.com/u/2660262?v=3","gravatar_id":"","url":"https://api.github.com/users/sandorfr","html_url":"https://github.com/sandorfr","followers_url":"https://api.github.com/users/sandorfr/followers","following_url":"https://api.github.com/users/sandorfr/following{/other_user}","gists_url":"https://api.github.com/users/sandorfr/gists{/gist_id}","starred_url":"https://api.github.com/users/sandorfr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sandorfr/subscriptions","organizations_url":"https://api.github.com/users/sandorfr/orgs","repos_url":"https://api.github.com/users/sandorfr/repos","events_url":"https://api.github.com/users/sandorfr/events{/privacy}","received_events_url":"https://api.github.com/users/sandorfr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-21T23:39:06Z","updated_at":"2016-06-21T23:39:06Z","closed_at":null,"body":"I maintain an Azure table logger since beta3, and because this thing is bugging me since then, I never published it.\r\n\r\nBegingScope has to be implemented as a generic method, but it has no constraint of any kind. It feels almost pointless. Moreover, builtin loggers are not leveraging it.\r\n\r\nMy first guess was that is was intended as an easier way to allow us to do some cached code generation. But, from what I observed, it seems like the team committed to states deriving from `IReadOnlyList<KeyValuePair<string, object>>`. In that case add a constraint on TState, it's just an interface so it is easy to implement for anyone willing to provide a custom scope. \r\n\r\nThis would make it much easier and useful  when supporting scopes.\r\n\r\n"}}
{"actor":{"display_login":"sandorfr"}}