Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phillipcarter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
98 ms
·
1291.
▲
by
phillipcarter
10y ago
Author of the article here. Happy to see this up on HN! The article is actually more of an annotated version of the F# Tutorial Script[0] which ships inside Visual Studio 2017 (also in other version of Visual Studio, but the Tutorial scrip
1292.
▲
by
phillipcarter
10y ago
Awkward person in the video here... Let me see if I can clarify the landscape a bit here: .NET Core tooling support is still in absolute Preview. The runtime and libraries are stable, but the .NET Core SDK, MSBuild support for .NET Cor
1293.
▲
by
phillipcarter
10y ago
> In other words, I think the language is way ahead of the libraries and tooling - there is so much more that can be done (and is being done) using F# as-is! I completely agree! I wish I had more upvotes to give, since I'd give your
1294.
▲
by
phillipcarter
10y ago
Awkward person in the video AND author of that tutorial here... I'd love to learn more about what went wrong in setup. Keeping that article up to date and, more importantly, correct is a priority of mine, because I really want peo
1295.
▲
by
phillipcarter
10y ago
Hey tomas! This is why I love working on an open project like F#. We get to disagree in public ! I would actually like Typeclasses, though I have serious reservations in terms of not breaking back compatibility. I'm certainly not a
1296.
▲
by
phillipcarter
10y ago
Awkward person who was in the video here The issue you're looking for (since an ask for HKTs typically means that Typeclasses are the ideal feature) is here: https://github.com/fsharp/fslang-suggestions/is
1297.
▲
by
phillipcarter
10y ago
> It's also sad to see no mention of really improved tooling, to put F# on the level of C#. Could you clarify what you mean here? Perhaps I could have written more about it in the blog post, but sitting the language service atop th
1298.
▲
by
phillipcarter
10y ago
To build off of enricosada's post, this is indeed being tracked and actively worked on right now. More information here: https://github.com/dotnet/cli/issues/3705#issuecomment-22889... Known issues will