Skip to content

Commit

Permalink
small tweaks
Browse files Browse the repository at this point in the history
  • Loading branch information
JRMurr committed Dec 3, 2023
1 parent 5be4eab commit f832916
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion data/blog/efficient-nix-derivations-with-file-sets.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Now with this setup, we have a "base" file set of `[ ./Makefile ./src ]` then wi
## A Real Example

Recently I started messing around with the language [Roc](https://www.roc-lang.org/). If you haven't heard of it, Roc is a new functional language heavily inspired by Elm.
It's fast but also very nice to use (though many rough edges since it's pre-0.1.0).
It's fast but also very nice to use (though some rough edges since it's pre-0.1.0).

One of its interesting ideas is that Roc needs your app to pick what [platform](https://www.roc-lang.org/platforms) to run on.
A platform would be written in something like rust, zig, c, etc.
Expand All @@ -79,6 +79,7 @@ Right now the two most widely used are a [cli platform](https://github.com/roc-l

This is really neat but brings an issue for developing a platform along with the roc code needed to define the platform API.
You need to compile the "platform code" (ie rust + some c), do w/e linking is needed for that, then distribute that with the roc source code.
The roc cli will do this for you when developing but it doesn't work as nicely for a build with nix.

For example, [this](https://github.com/roc-lang/roc/tree/main/examples/platform-switching/rust-platform) is one of the sample platforms

Expand Down

0 comments on commit f832916

Please sign in to comment.