chusk3

5 ms·

1.
by chusk3 1y ago
It also solves a more subtle problem - when people install a tool globally they install latest _at that time_. But the world doesn't stand still, and things get updated. `dnx` always uses the latest available version by default (you ca
2.
by chusk3 2y ago
Hi, I'm the maintainer for the VSCode F# support. Rider support for F# is great, that team is very engaged, and I'd strongly consider it if * you have mixed C#/F# projects in a solution (C# and F# support in VSCode can'
3.
by chusk3 3y ago
Capturing these guidelines is one of the primary reasons that https://clig.dev/ exists.
4.
by chusk3 3y ago
They've worked for several years now on dotnet, but the type provider author has to do some work to allow their type provider to compile and target that runtime.
5.
by chusk3 4y ago
We've been baking this functionality directly into the .NET SDK for a couple releases now: https://github.com/dotnet/sdk-container-builds It's really nice to derive mostly-complete container images from infor
6.
by chusk3 4y ago
Assuming you're talking about FsAutoComplete and this was recently, that's nothing to do with the .NET Runtime and entirely a coding mistake that I made that we've released a fix for :)
7.
by chusk3 4y ago
There is some benefit to building inside a container - it keeps your build environment consistent across team members and makes it easier to replicate your CI. Having said that, because the .Net toolchain is capable of cross-targeting this
8.
by chusk3 4y ago
You make great points about the need for customization and the boundaries of solutions that aren't based on Dockerfiles. Our approach to that problem is twofold, though both parts are still only in the planning stage: * eventually prov
9.
by chusk3 4y ago
IMO running a managed runtime like .NET inside a container isn't done as a security measure (like sandboxing) - instead it's done for uniformity and ease of deployment to the infinite number of cloud services/hosting provider
10.
by chusk3 4y ago
Mainly what I was getting at here is that there are often repo-level files that are part of the .NET build process that are easy to forget to include in your build context/as part of the initial COPY command that most folks to do to a
11.
by chusk3 4y ago
Hey folks - author here, happy to answer any questions about the feature or what we're hoping to do with it. Broadly we just want to lower barriers to containerization for all .NET developers. Jib/Ko/etc are proven patterns i
12.
by chusk3 5y ago
This is similar in aim to FSharp.Formatting[1], which has been used for a while to generate syntax highlighting and hover tooltips for code samples and API docs in the F# ecosystem. Very cool to see! [1]: https://github.com/
13.
by chusk3 5y ago
In F# we call it 'collect' instead, partially for this reason.
14.
by chusk3 5y ago
Nitpick here = the `Load` member takes a path to _any_ file of the same schema as the sample, but you can also just use the sample at runtime with the use of `Load()`. So it doesn't have to be as redundant as you've shown here, th
15.
by chusk3 5y ago
Yeah, there are four standout features for me in this release: * resumable code for computation expressions - zero-overhead, ergonomic state machines that are user-extensible! really excited to see what folks dream up with this. * overloadi
16.
by chusk3 5y ago
I wouldn't do this, as this is the mono bundle of fsharp. The blessed/supported way to go now is to install the dotnet-sdk packages[1] and then use `dotnet fsi` for interactive work, and `dotnet build/run/etc` for projec
17.
by chusk3 5y ago
Please use the appropriate name for the person in question. Claire is her name.
18.
by chusk3 5y ago
I'm not at all sure what you mean by 'typescript docs' in your comment. The protocol for things like tooltips/signature completion literally just says 'put arbitrary markdown here'. It doesn't proscribe t
19.
by chusk3 5y ago
That's simply not true; there are LSP client implementations/integrations for vim, neovim, emacs, sublime text, web environments like gitpod.io, Eclipse IDE (via Theia IDE), Jetbrains supports it in their IDEs, and Visual Studio e
20.
by chusk3 6y ago
Worth noting that snap installs aren't supported in the vscode tooling for F#. There's an open issue and I have a handle on some of the core problems, but they invalidate a ton of assumptions we have. The safer route is to install
21.
by chusk3 7y ago
Yes, and the F# library for asynchronous sequence processing had support added for them shortly thereafter ( https://fsprojects.github.io/FSharp.Control.AsyncSeq/library... )
22.
by chusk3 7y ago
For clarity, the position is that large features like TC/HKT won't be added in a way that could conflict with a later-added .net/IL version of the feature.
23.
by chusk3 7y ago
A big push in .net core 2.x and 3.x was what we call the Span-ification of the base class library and the runtime. This means there are many new APIs for dealing with slices of memory in a non-allocating manner, and this combined with memor
24.
by chusk3 7y ago
You can choose to do a self-contained deployment, which bundles the runtime with your app, or a framework-dependent deployment, which requires a pre-existing shared install. Pick your poison.
25.
by chusk3 7y ago
I'd say more like Elm's Pheonix LiveView, to be honest.
26.
by chusk3 7y ago
on the free plan it caps at 100GB of total stored logs, which then rotate out. It's great if you don't care about super-old logs.
27.
by chusk3 7y ago
This is silly, F# has never been more of a first-class citizen. It's explicitly part of the .net core distributions, part of the nightly testing and validation cycles, and is in the TechEmpower benchmarks.
28.
by chusk3 7y ago
For my money your type provider was the single coolest one I've seen before. The ahead of time query execution and planning is a killer feature, and for us the only gaps were either process related, meaning we did not have a good out-o
29.
by chusk3 7y ago
Yes, that's the case. However there's also the 'merge this when the build successfully completes' that means you can push one button and walk away. They are also developing features around MRs that 'ripple' in
30.
by chusk3 7y ago
Right now I have a one button rebase operation in gitlab, and if that does work (due to conflicts) then I'm at a situation I want to be in: verifying that my changes integrate cleanly.

More ›