-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should the SDK be named csharp? #13
Comments
Then comes the discussion around the new features of dagger It may be better to actually split and focus on a csharp named sdk, and if f# is popular, F# sdk should be made (which could still potentially have some benefits of any shared .net code) - One idea is that a CSharp Project is used to generate the C# SDK from the source generator and a main F# project is used which pulls in those C# generated types. This is supposedly what a lot of F# developers do. They do sometimes require C# Projects due to the popularity of C#. |
Yeah, this is my original goals that I hope this SDK would be. I've try with F# recently at #14. The code is a bit ugly but its works. 🙈 My thought is we can write the SDK with C# and make language in the family (F#, PowerShell, etc.) calling this SDK. I'm not sure if we need a small wrapper to make DX better for the language. We can discover it after make C# works. :) For the
However, we might need to write a module runtime library to load the code (C# method, F# function) to register module into the Dagger Engine (like Go main function does in |
Reason for this issue:
.NET SDK generally would mean support for any language on the .NET runtime
Source Generators (Roslyn) is unique to C# but there does seem to be discussions within F# community on redirecting compilation from
csc
(C# compiler) and taking theIL
to incorporate into F#.fsharp/fslang-suggestions#864
The text was updated successfully, but these errors were encountered: