Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle nix symbolic strings on Nix side #153

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Handle nix symbolic strings on Nix side #153

wants to merge 2 commits into from

Commits on Sep 29, 2023

  1. Handle nix symbolic strings on Nix side 

    This allows us to shortcut usage of NixString in many places.
We could probably get rid of NixString entirely as well, but it needs
more consideration.

Part of #58.
    @YorikSar
    YorikSar committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    136b6be View commit details
    Browse the repository at this point in the history

  2. Get rid of the original encoding of Nix strings 

    Directly using Nickel's encoding for symbolic strings is as powerful,
and simpler since it means that `nix-s%"blah"%` is a valid Nix string,
while we previously had to explicitly apply the `NixString` contract.
    Théophane Hufschmitt committed Sep 29, 2023
    Configuration menu
    Copy the full SHA
    78e972e View commit details
    Browse the repository at this point in the history