Robert Hensing

> just put them in the devShell. Strictness isn't the only problem. These ~scripts~ commands cannot be made aware of the project root. In non-flake Nix, you could use `${toString...

> Maybe we could make `nix develop` export `FLAKE_ROOT` as you suggest for the dev tools? This will be redundant when `nix develop` is powered by `nix dev shell`, which...

My working hypothesis is that the `^` points (correctly) at the start of the Expr. If that's an `ExprCall`, the start of the call is equal to the start of...

@gilligan , thank you for your review. I have implemented all of your suggestions except the `nixdoc:`. I'm also a bit concerned about the ugly comments that might show up....

@gilligan I agree that we need some kind of marker to indicate that it's a documentation comment. I think `/**` or `##` should be sufficient, but it's also nice to...

Before the holidays, I put out a twitter poll about the syntax for documentation comments. The results: It got 24 votes: > 33% /** always plain text */ (8 people)...

@edolstra good. What about an extensible syntax marked by a keyword right after `/**`? Or do you want to 'disallow' plain text (most comments now) and standardize on a single...

Before this can be merged we have to make decisions about syntax, because this code will return FIXME comments and such.

> Before this can be merged we have to make decisions about syntax, because this code will return FIXME comments and such. What I really should have done back then...

What makes use abuse? Aren't comments equally controllable? By turning comments into annotations, you enable _static_ introspection, so that you don't have to burden the interpreter with it. Evaluation performance...