Forwarded from システム
NDC Oslo 2018 | Software Developers Conference
The F# Path To Relaxation - NDC Oslo 2018 | Software Developers Conference
Born in a lab, matured in the enterprise, and now fully baked as an open-source, cross-platform, professionally-supported language: the F# journey has always been about reconciling the apparently irreconcilable. Javascript and .NET, Linux and Windows, Functional…
Forwarded from システム
@neftedollar @gsomix @vshapenko @AnutaU
Hi there, a short update on questions:
1) Type providers parameterized by types - is being developed by only one person, so ETA - next major F# release after this person will be ready, but we are strongly encouraged to help;
2) SRTP fixes - ETA F# 5
3) Traits, type classes or something like that - when general architecture picture will be agreed with rest of .NET language architects, specifically Mads, ETA unknown, but maybe around C# 8.0;
4) Anonymous records - they are ready, but the reason why they are not in F# 4.5 - not enough feedbacks and tests from the community, ETA - F# 5.0;
5) Reason why there are no parameterized modules in F# in the same way as in OCaml - primarily because of possible community split like in Scala, when 50% use it, and another 50% don't use it, and missing of clear picture how to constraint such feature in a right way, but it could be added if there would be enough requests;
6) Task computational expression recognizable by the compiler - ETA F# 5.0;
Hi there, a short update on questions:
1) Type providers parameterized by types - is being developed by only one person, so ETA - next major F# release after this person will be ready, but we are strongly encouraged to help;
2) SRTP fixes - ETA F# 5
3) Traits, type classes or something like that - when general architecture picture will be agreed with rest of .NET language architects, specifically Mads, ETA unknown, but maybe around C# 8.0;
4) Anonymous records - they are ready, but the reason why they are not in F# 4.5 - not enough feedbacks and tests from the community, ETA - F# 5.0;
5) Reason why there are no parameterized modules in F# in the same way as in OCaml - primarily because of possible community split like in Scala, when 50% use it, and another 50% don't use it, and missing of clear picture how to constraint such feature in a right way, but it could be added if there would be enough requests;
6) Task computational expression recognizable by the compiler - ETA F# 5.0;
Forwarded from gsomix
YouTube
The F# Path to Relaxation by Don Syme
Born in a lab, matured in the enterprise, and now fully baked as an open-source, cross-platform, professionally-supported language: the F# journey has always been about reconciling the apparently irreconcilable. Javascript and .NET, Linux and Windows, Functional…
Forwarded from Ayrat Hudaygulov
Forwarded from Vagif Abilov
Это демо нашего с Павлом доклада на NDC Oslo, там все примеры запускались в Visual Studio Code.
Forwarded from devdigest // dot net (dotnet)
В новом выпуске Channel 9 Phillip Carter расскажет о разработке Web API на F# и .NET Core
https://devdigest.today/post/563
https://devdigest.today/post/563
Developers Digest
Web API development with F# on .NET Core
In this episode, Phillip Carter (@_cartermp) returns to continue our conversation about programming with F#. This time he's talking to us about how to get started with web API programming with F#, and
Forwarded from Sergey Tihon
есть тут Heroes? https://twitter.com/FableCompiler/status/1017814519853277184
Twitter
Fable
Following the healthy habits of our @c4fsharp brothers, this year we'll have our own Fable Community Heroes! The winners will be announced at #fableconf but for that you first need to nominate the best contributors to Fable ecosystem in 2018! #fsharp htt…
Creating a Windows Forms GUI with F# – Ville M. Vainio – Medium
https://medium.com/@vivainio/creating-a-windows-forms-gui-with-f-968b3ae75a82
https://medium.com/@vivainio/creating-a-windows-forms-gui-with-f-968b3ae75a82
Medium
Creating a Windows Forms GUI with F#
Windows Forms is not dead — it’s now more alive than it has been for years now that Microsoft announced they will support it in .NET Core…