3 ms·
Because it's a statically typed language it's all in the IDE. Almost everyone who uses C# doesn't need to check the documentation for that kind of information,
by mattmanser 11y ago
Because it's a statically typed language it's all in the IDE. Almost everyone who uses C# doesn't need to check the documentation for that kind of information, it comes up when you're typing, or it's an ctrl-space away if your caret is on a method, or you can right-click go to definition.
You can pretty much right click on anything and go to definition, which will show you all the method signatures and return types of everything.
My only beef with the documentation is that they show examples of the code in use, but annoyingly never the output. So, for example, it's never clear even from the examples in the documentation whether a directory path or a URL includes a trailing slash or not. And because there's no REPL, you have to either build/compile/run or use an external program (I used to use some LINQ tester program that was basically a REPL, but it's contextually almost as expensive as simply trying it in an existing program).
- Locke1689 11y ago> And because there's no REPL Working on it -- you can expect a public pre-release soon. The code is in master right now: https://github.com/dotnet/roslyn/tree/master/src/InteractiveWindow https://github.com/dotnet/roslyn/tree/master/src/Interactive.... I'll have to check with the dev to see how installing it is supposed to work, but he demo'd it on Friday and it looked very slick.
- mattmanser 11y agoThat will be a wonderful addition!
- jimktrains2 11y ago> Because it's a statically typed language it's all in the IDE. What if you don't want to use VS directly? Also, if it's "all in the IDE" why have it online at all? And if it is on line, why not just include the return type?