-
Notifications
You must be signed in to change notification settings - Fork 85
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
IFD like behavior #623
Comments
Hey, thanks for asking! We are not there yet, but yes, the motivation of effects is precisely to be a generic way of implementing things like IFD in Nix, or similar situations in cloud deployment, when you need one machine to be deployed first before getting an IP and deploy another machine that depends on it. As commented in #85 (comment), this subject has been on hold until now, because we focused on the core language, but may make a return soon, because the next step on the roadmap is to start to actually elaborate a solid plan to use Nickel for Nix. |
Cool! Can't wait honestly! Nix isnt such a bad language as some make it out to be but Nickel is definitely a solid step up. |
Is your feature request related to a problem? Please describe.
Nope
Describe the solution you'd like
No clue, I'm wondering whether IFD as we know and love(hate) it from Nix will make a return.
Describe alternatives you've considered
Not having IFD and relying on X2nickel projects... (please no)
Additional context
I'm guessing it could somehow be implemented as an #85 internal effect. If done that way it would have to be explicit which is imo a good thing.
The text was updated successfully, but these errors were encountered: