Join Kit Eason for an in-depth discussion in this video Contributing to F# and its tooling, part of What's New in Visual Studio 2017 for F# For Developers.
- [Instructor] Before we wrap up,…I just want to take a moment…to acknowledge the enormous open source contribution…that's been made to F# 4.1…and its visual studio Tooling…and maybe even to encourage you to join in.…So just to get an idea of the scale of things,…here's the guitar page for Visual F#…and I'm looking at the pulse area that tells you…how many contributions are going on.…So we've got 76 merged PRs, 13 proposed PRs,…51 closed issues, 33 new issues, 14 authors,…and that's over the past month.…
That's fairly impressive.…Just to give you an idea of the scale of it,…I'm going to head on over to the equivalent page…for the node part of Node.js…and as you can see the statistics…although they are somewhat bigger…are generally on the same order of magnitude.…So that's a pretty impressive thing.…If you want to join the party,…you need to go to guitar.com/Microsoft/visualfsharp…where there's a truly wonderful guide…to how you can contribute…and there are contributions available at many levels…from simply things like phrasing error messages…
Kit Eason discusses the new value types that provide an opportunity for performance gains, the new result type which gives you access to the railway oriented programming style of error handling, and program organization and readability changes. Plus, he explores the evolution of tooling for F#, and explains how F# tooling has changed in Visual Studio 2017. To wrap up the course, he shares how you can contribute to the F# language and tooling by getting involved in the open-source community.
- Working with struct tuples
- Marking a record type as a struct value
- Marking a discriminated union as a struct type
- Using the fixed keyword to mark a value
- F# result type and associated functions
- Resolving potential naming clashes between modules and types
- Error message improvements
- The past and future of visual F# tooling in Visual Studio
- Reviewing F# tooling changes