{"action":"created","issue":{"url":"https://api.github.com/repos/dotnet/standard/issues/682","repository_url":"https://api.github.com/repos/dotnet/standard","labels_url":"https://api.github.com/repos/dotnet/standard/issues/682/labels{/name}","comments_url":"https://api.github.com/repos/dotnet/standard/issues/682/comments","events_url":"https://api.github.com/repos/dotnet/standard/issues/682/events","html_url":"https://github.com/dotnet/standard/issues/682","id":306198723,"node_id":"MDU6SXNzdWUzMDYxOTg3MjM=","number":682,"title":".Net Standard 2.1?","user":{"login":"RussKeldorph","id":15160879,"node_id":"MDQ6VXNlcjE1MTYwODc5","avatar_url":"https://avatars3.githubusercontent.com/u/15160879?v=4","gravatar_id":"","url":"https://api.github.com/users/RussKeldorph","html_url":"https://github.com/RussKeldorph","followers_url":"https://api.github.com/users/RussKeldorph/followers","following_url":"https://api.github.com/users/RussKeldorph/following{/other_user}","gists_url":"https://api.github.com/users/RussKeldorph/gists{/gist_id}","starred_url":"https://api.github.com/users/RussKeldorph/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RussKeldorph/subscriptions","organizations_url":"https://api.github.com/users/RussKeldorph/orgs","repos_url":"https://api.github.com/users/RussKeldorph/repos","events_url":"https://api.github.com/users/RussKeldorph/events{/privacy}","received_events_url":"https://api.github.com/users/RussKeldorph/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":103,"created_at":"2018-03-17T23:21:04Z","updated_at":"2018-06-02T19:07:24Z","closed_at":null,"author_association":"MEMBER","body":"_From @jherby2k on March 7, 2018 19:35_\n\nI can't find any information about a .net standard 2.1.\r\n\r\nI really want to use the new Span-ified methods like Stream.Read in my class libraries, but it looks like that stuff isn't in System.Memory but rather the .net core 2.1 SDK. Any other way to get these APIs, or do I have to wait for .net standard 2.1. And is there any ETA on that?\n\n_Copied from original issue: dotnet/coreclr#16806_"},"comment":{"url":"https://api.github.com/repos/dotnet/standard/issues/comments/394109567","html_url":"https://github.com/dotnet/standard/issues/682#issuecomment-394109567","issue_url":"https://api.github.com/repos/dotnet/standard/issues/682","id":394109567,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NDEwOTU2Nw==","user":{"login":"jherby2k","id":9419251,"node_id":"MDQ6VXNlcjk0MTkyNTE=","avatar_url":"https://avatars2.githubusercontent.com/u/9419251?v=4","gravatar_id":"","url":"https://api.github.com/users/jherby2k","html_url":"https://github.com/jherby2k","followers_url":"https://api.github.com/users/jherby2k/followers","following_url":"https://api.github.com/users/jherby2k/following{/other_user}","gists_url":"https://api.github.com/users/jherby2k/gists{/gist_id}","starred_url":"https://api.github.com/users/jherby2k/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jherby2k/subscriptions","organizations_url":"https://api.github.com/users/jherby2k/orgs","repos_url":"https://api.github.com/users/jherby2k/repos","events_url":"https://api.github.com/users/jherby2k/events{/privacy}","received_events_url":"https://api.github.com/users/jherby2k/received_events","type":"User","site_admin":false},"created_at":"2018-06-02T19:07:24Z","updated_at":"2018-06-02T19:07:24Z","author_association":"NONE","body":"I take full responsibility for starting this thread. My original question was simply what was the ETA for .NET Standard 2.1 (and by extension a Spanified full framework). Sounds like I'm waiting on .NET Standard 3.0 / Framework 4.8, which are coming some time next year. \r\n\r\n\r\nAs to the satellite discussion, I don't completely buy the argument for why it needs to be a trailing standard. Having a leading standard would mean I don't have to repackage my netcoreapp2.1 library as netstandard3.0. For Microsoft, this means better adoption of the standard in library code.\r\n\r\n\r\nIts worth pointing out that the \"spanification\" of a huge base of otherwise preexisting API surface is a bit of an edge case, and things like this won't come up often. Usually new APIs can and will show up in nuget packages. So new standard releases might be rare anyhow."}}
{"actor":{"display_login":"jherby2k"}}