{"action":"created","issue":{"url":"https://api.github.com/repos/dotnet/roslyn/issues/122","labels_url":"https://api.github.com/repos/dotnet/roslyn/issues/122/labels{/name}","comments_url":"https://api.github.com/repos/dotnet/roslyn/issues/122/comments","events_url":"https://api.github.com/repos/dotnet/roslyn/issues/122/events","html_url":"https://github.com/dotnet/roslyn/issues/122","id":55796915,"number":122,"title":"Interactive Design Meeting Notes - 1/23/15","user":{"login":"kuhlenh","id":1402694,"avatar_url":"https://avatars.githubusercontent.com/u/1402694?v=3","gravatar_id":"","url":"https://api.github.com/users/kuhlenh","html_url":"https://github.com/kuhlenh","followers_url":"https://api.github.com/users/kuhlenh/followers","following_url":"https://api.github.com/users/kuhlenh/following{/other_user}","gists_url":"https://api.github.com/users/kuhlenh/gists{/gist_id}","starred_url":"https://api.github.com/users/kuhlenh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kuhlenh/subscriptions","organizations_url":"https://api.github.com/users/kuhlenh/orgs","repos_url":"https://api.github.com/users/kuhlenh/repos","events_url":"https://api.github.com/users/kuhlenh/events{/privacy}","received_events_url":"https://api.github.com/users/kuhlenh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/dotnet/roslyn/labels/Area-Debugging","name":"Area-Debugging","color":"5319e7"},{"url":"https://api.github.com/repos/dotnet/roslyn/labels/Area-Interactive%20Design","name":"Area-Interactive Design","color":"5319e7"}],"state":"open","locked":false,"assignee":{"login":"kuhlenh","id":1402694,"avatar_url":"https://avatars.githubusercontent.com/u/1402694?v=3","gravatar_id":"","url":"https://api.github.com/users/kuhlenh","html_url":"https://github.com/kuhlenh","followers_url":"https://api.github.com/users/kuhlenh/followers","following_url":"https://api.github.com/users/kuhlenh/following{/other_user}","gists_url":"https://api.github.com/users/kuhlenh/gists{/gist_id}","starred_url":"https://api.github.com/users/kuhlenh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kuhlenh/subscriptions","organizations_url":"https://api.github.com/users/kuhlenh/orgs","repos_url":"https://api.github.com/users/kuhlenh/repos","events_url":"https://api.github.com/users/kuhlenh/events{/privacy}","received_events_url":"https://api.github.com/users/kuhlenh/received_events","type":"User","site_admin":false},"milestone":null,"comments":6,"created_at":"2015-01-28T18:40:01Z","updated_at":"2015-01-29T06:24:07Z","closed_at":null,"body":"Interactive Design Meeting Notes - 1/23/15\r\n==========================================\r\n\r\nDefinitions\r\n-------------\r\n - **REPL:** a read-eval-print-loop is a tool that allows developers to execute code snippets in a user-supplied context\r\n - **Scripting:** a light-weight solution for writing simple and small programs. Includes an API for users to execute scripts in host-supplied applications\r\n - **Interactive Window:** the Visual Studio component that will host the interactive modes of languages\r\n - **Design-time**, also referred to as \"standalone,\" includes scenarios that are not attached to a debugger process\r\n - **Debug-time**, also referred to as the \"immediate window,\" includes scenarios that are attached to a debugger process\r\n  \r\n\r\nDesign Team\r\n-------------\r\nThe following individuals are members of the dream team:\r\n[Anthony D. Green](https://github.com/AnthonyDGreen)\r\n[Chuck Stoner](https://github.com/CharlesStoner)\r\n[Dustin Campbell](https://github.com/DustinCampbell)\r\n[Kasey Uhlenhuth](https://github.com/kuhlenh)\r\n[Kevin Halverson](https://github.com/KevinH-MS)\r\n[Kevin Pilch-Bisson](https://github.com/Pilchie)\r\n[Lincoln Atkinson](https://github.com/latkin)\r\n[Manish Jayaswal](https://github.com/ManishJayaswal)\r\n[Matt Warren](https://github.com/mattwar)\r\n[Tomas Matousek](https://github.com/tmat)\r\n\r\n*Special Guests:*\r\n[Mads Torgersen](https://github.com/MadsTorgersen)\r\n[Neal Gafter](https://github.com/gafter)\r\n\r\n\r\nAbout the Design Process\r\n------------------------\r\n\r\nWe meet for 2 hours a week to sketch final designs and experiences for Interactive. It is usually up to Kasey to determine the topic for discussion.\r\n\r\nMeeting notes will be shared publicly on the dotnet/roslyn GitHub so that the community can respond and give input on our thoughts. Notes will be posted as *issues* thus allowing the community to comment on the thread. We will take comments into consideration for the next meeting.\r\n\r\nUltimately, the Interactive Design team is still in charge of the interactive intiative. This is not a democratic process; the team will make the final decisions. That said, we will look at UserVoice, comments on notes, and feature requests. \r\n\r\n----------\r\n\r\n\r\nAgenda: Interactive Language Semantics\r\n--------------------------------------\r\n\r\nHappy New Year! This meeting focused on design-time language semantics and experiences for the REPL and Scripting. \r\n\r\n#### LANGUAGE FEATURES\r\n> **Note:**\r\n> The REPL and scripts contain *top-level code*. This means a user should feel like he/she is typing at the namespace, class, and/or method-body level. \r\n\r\n- **Async/await**:\r\n\t- REPL: We determined to always use “await” as a keyword. In the scenario “await x; await y;” it is confusing to determine if this is happening concurrently. \r\n\t\t- *Solution*: We will block the execution thread until the await returns (the user can still scroll but will not get the next prompt. AKA the REPL will not take any more input until the await is complete).\r\n\t- Scripting: We considered having scripts always be in the async context. We also considered making async/await illegal in scripts or only allowing it outside the top-level.\r\n\t\t- *Solution*: Because the REPL uses the Scripting API, we have to support async/await everywhere.\r\n- **Other recent language features:** There should be no special circumstances for the use of string interpolation, null-conditional operators, index intializers, exception filters, expression-bodied function members, using static, and other C# 6.0 language features. \r\n\r\n#### OTHER FEATURES\r\n\r\n- **Variables/fields:** We will allow top-level fields in the REPL and scripts. Static variables WILL NOT be allowed. Read-only variables WILL be allowed. \r\n-  **Hiding/shadowing definitions:** \r\nThe following code snippet (in a C# REPL) demonstrates definition shadowing. The latter definition of `x` \"hides\" the previous one but does not replace previous instances.\r\n<pre><code>c#> int x = 4;\r\nc#> int y = x+3;\r\nc#> y\r\n7\r\nc#> int x = 5;\r\nc#> y\r\n7\r\nc#> x\r\n5\r\n </pre></code>\r\n   \r\n- **New Directives:**\r\n\t- **#r** : Allows a developer to reference a .dll or NuGet package\r\n\t- **#load** : Allows a developer to set context with source or script files. It essentially acts as if the developer copy/pasted the file into the script or REPL session. Order for #loads is critical in script files because of their linear execution.\r\n\t  \t>**Note:**\r\n\t\t> A developer will not be allowed to #load a .cs file because we do not allow namespaces in Interactive semantics. If we have time, we can write an API to allow this functionality.\r\n\r\n\t- **#r!** : Allows a developer to reference a .dll with access to its internals.\r\n\t\t> **Problem**: \r\n\t\t>  We believe developers should be able to load a .dll with access to internals (this is how you can “seed from a project”). Top scenarios for “seeding” are writing a unit test script and testing/interacting with a project in the REPL. However, we believe only some .dlls should be accepted by the host. A developer should only be able to load a .dll with internal access on personal projects (there are no scenarios that we want this support for that do not involve the user’s source). TODO: Write a proposal for a policy for when our host will load a .dll with internals\r\n\r\nNext time we will discuss incorporating F# directives: **#l** (adds “some path” to assembly and script resolution search path) and **#time** (turns on simple perf stats--Real, CPU, GC--for each evaluated command)"},"comment":{"url":"https://api.github.com/repos/dotnet/roslyn/issues/comments/71975255","html_url":"https://github.com/dotnet/roslyn/issues/122#issuecomment-71975255","issue_url":"https://api.github.com/repos/dotnet/roslyn/issues/122","id":71975255,"user":{"login":"tmat","id":41759,"avatar_url":"https://avatars.githubusercontent.com/u/41759?v=3","gravatar_id":"","url":"https://api.github.com/users/tmat","html_url":"https://github.com/tmat","followers_url":"https://api.github.com/users/tmat/followers","following_url":"https://api.github.com/users/tmat/following{/other_user}","gists_url":"https://api.github.com/users/tmat/gists{/gist_id}","starred_url":"https://api.github.com/users/tmat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmat/subscriptions","organizations_url":"https://api.github.com/users/tmat/orgs","repos_url":"https://api.github.com/users/tmat/repos","events_url":"https://api.github.com/users/tmat/events{/privacy}","received_events_url":"https://api.github.com/users/tmat/received_events","type":"User","site_admin":false},"created_at":"2015-01-29T06:24:07Z","updated_at":"2015-01-29T06:24:07Z","body":"https://github.com/dotnet/roslyn/blob/master/src/Compilers/Core/Portable/MetadataReference/MetadataReferenceResolver.cs\r\n\r\nIt's probably not exposed via the hosting APIs yet."}}