Did you know that the #fsharp community has an official mentorship program? 100% free, community-driven, and has led to people being able to adopt F# in their workplace. CHECK IT OUT!
https://fsharp.org/mentorship/about.html
https://fsharp.org/mentorship/about.html
F# Weekly #21, 2018 – .NET Core 2.1 & F# Relaxation achieved, 200%
https://sergeytihon.com/2018/05/26/f-weekly-21-2018-net-core-2-1-f-relaxation-achieved-200/
https://sergeytihon.com/2018/05/26/f-weekly-21-2018-net-core-2-1-f-relaxation-achieved-200/
Sergey Tihon's Blog
F# Weekly #21, 2018 – .NET Core 2.1 & F# Relaxation achieved, 200%
Welcome to F# Weekly, A roundup of F# content from this past week: News .NET Core 2.1 releasing next week, May 30 FSharpx.Collections 2.0 release plan F# Tutorial on TutorialsPoint Do not miss your…
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