Viewing profile — chusk3
chusk3
HN member- Joined
- Tue, Sep 26, 2017, 9:09 PM UTC
- HN karma
- 106
- Public activity
- 48 items
- HN profile
- View on Hacker News ↗
About chusk3
No profile information was provided.
Recent public activity
-
comment
Comment #44735816
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` alwa…
-
comment
Comment #41937601
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 sol…
-
comment
Comment #38971118
Capturing these guidelines is one of the primary reasons that https://clig.dev/ exists.
-
comment
Comment #38163088
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.
-
comment
Comment #34684686
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…
-
comment
Comment #32666335
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 f…
-
comment
Comment #32633916
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, be…
-
comment
Comment #32628974
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 …
-
comment
Comment #32628828
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 infin…
-
comment
Comment #32625537
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 …
-
comment
Comment #32625519
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…
-
comment
Comment #29970694
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…
-
comment
Comment #29813196
In F# we call it 'collect' instead, partially for this reason.
-
comment
Comment #29527122
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'…
-
comment
Comment #29165683
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! real…
-
comment
Comment #28865168
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 wor…
-
comment
Comment #28785616
Please use the appropriate name for the person in question. Claire is her name.
-
comment
Comment #26668419
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'…
-
comment
Comment #26668111
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), Jetbra…
-
comment
Comment #26033225
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 …
-
comment
Comment #21991146
Yes, and the F# library for asynchronous sequence processing had support added for them shortly thereafter ( https://fsprojects.github.io/FSharp.Control.AsyncSeq/library... )
-
comment
Comment #21991126
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.
-
comment
Comment #21916193
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 mem…
-
comment
Comment #21387047
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 y…
-
comment
Comment #21139236
I'd say more like Elm's Pheonix LiveView, to be honest.