2004-01-30 17:21:42 +02:00
|
|
|
|
%glr-parser
|
2019-10-09 23:57:37 +03:00
|
|
|
|
%define api.pure
|
2004-01-30 17:21:42 +02:00
|
|
|
|
%locations
|
2019-03-27 22:09:31 +02:00
|
|
|
|
%define parse.error verbose
|
2006-10-02 17:43:15 +03:00
|
|
|
|
%defines
|
2006-10-12 00:59:33 +03:00
|
|
|
|
/* %no-lines */
|
2013-03-14 19:31:08 +02:00
|
|
|
|
%parse-param { void * scanner }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
%parse-param { nix::ParserState * state }
|
2013-03-14 19:31:08 +02:00
|
|
|
|
%lex-param { void * scanner }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
%lex-param { nix::ParserState * state }
|
2012-04-13 15:28:26 +03:00
|
|
|
|
%expect 1
|
|
|
|
|
%expect-rr 1
|
2004-01-30 17:21:42 +02:00
|
|
|
|
|
2010-10-24 00:11:59 +03:00
|
|
|
|
%code requires {
|
2013-09-02 17:29:15 +03:00
|
|
|
|
|
2010-10-24 00:11:59 +03:00
|
|
|
|
#ifndef BISON_HEADER
|
|
|
|
|
#define BISON_HEADER
|
2013-09-02 17:29:15 +03:00
|
|
|
|
|
2022-01-19 14:39:42 +02:00
|
|
|
|
#include <variant>
|
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
#include "finally.hh"
|
2006-09-05 00:36:15 +03:00
|
|
|
|
#include "util.hh"
|
2023-10-25 07:43:36 +03:00
|
|
|
|
#include "users.hh"
|
2013-09-02 17:29:15 +03:00
|
|
|
|
|
2010-04-12 21:30:11 +03:00
|
|
|
|
#include "nixexpr.hh"
|
2011-08-06 19:05:24 +03:00
|
|
|
|
#include "eval.hh"
|
2023-07-31 16:19:19 +03:00
|
|
|
|
#include "eval-settings.hh"
|
2019-11-26 20:48:34 +02:00
|
|
|
|
#include "globals.hh"
|
2024-01-15 17:52:18 +02:00
|
|
|
|
#include "parser-state.hh"
|
2010-10-24 00:11:59 +03:00
|
|
|
|
|
2023-12-10 14:00:18 +02:00
|
|
|
|
#define YYLTYPE ::nix::ParserLocation
|
2010-10-24 00:11:59 +03:00
|
|
|
|
#define YY_DECL int yylex \
|
2024-01-15 17:52:18 +02:00
|
|
|
|
(YYSTYPE * yylval_param, YYLTYPE * yylloc_param, yyscan_t yyscanner, nix::ParserState * state)
|
2010-10-24 00:11:59 +03:00
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
namespace nix {
|
|
|
|
|
|
|
|
|
|
Expr * parseExprFromBuf(
|
|
|
|
|
char * text,
|
|
|
|
|
size_t length,
|
|
|
|
|
Pos::Origin origin,
|
|
|
|
|
const SourcePath & basePath,
|
|
|
|
|
SymbolTable & symbols,
|
|
|
|
|
PosTable & positions,
|
2024-01-15 17:52:18 +02:00
|
|
|
|
const ref<InputAccessor> rootFS,
|
|
|
|
|
const Expr::AstSymbols & astSymbols);
|
2024-01-15 17:52:18 +02:00
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
2010-10-24 00:11:59 +03:00
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
%{
|
|
|
|
|
|
2006-09-05 01:08:40 +03:00
|
|
|
|
#include "parser-tab.hh"
|
|
|
|
|
#include "lexer-tab.hh"
|
|
|
|
|
|
2010-10-24 00:11:59 +03:00
|
|
|
|
YY_DECL;
|
2006-09-05 00:36:15 +03:00
|
|
|
|
|
2006-09-05 00:06:23 +03:00
|
|
|
|
using namespace nix;
|
2004-01-30 17:21:42 +02:00
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
#define CUR_POS state->at(*yylocp)
|
2006-09-05 00:36:15 +03:00
|
|
|
|
|
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
void yyerror(YYLTYPE * loc, yyscan_t scanner, ParserState * state, const char * error)
|
2006-09-05 00:36:15 +03:00
|
|
|
|
{
|
2024-01-15 17:52:18 +02:00
|
|
|
|
throw ParseError({
|
2024-02-04 06:35:19 +02:00
|
|
|
|
.msg = HintFmt(error),
|
libexpr: Support structured error classes
While preparing PRs like #9753, I've had to change error messages in
dozens of code paths. It would be nice if instead of
EvalError("expected 'boolean' but found '%1%'", showType(v))
we could write
TypeError(v, "boolean")
or similar. Then, changing the error message could be a mechanical
refactor with the compiler pointing out places the constructor needs to
be changed, rather than the error-prone process of grepping through the
codebase. Structured errors would also help prevent the "same" error
from having multiple slightly different messages, and could be a first
step towards error codes / an error index.
This PR reworks the exception infrastructure in `libexpr` to
support exception types with different constructor signatures than
`BaseError`. Actually refactoring the exceptions to use structured data
will come in a future PR (this one is big enough already, as it has to
touch every exception in `libexpr`).
The core design is in `eval-error.hh`. Generally, errors like this:
state.error("'%s' is not a string", getAttrPathStr())
.debugThrow<TypeError>()
are transformed like this:
state.error<TypeError>("'%s' is not a string", getAttrPathStr())
.debugThrow()
The type annotation has moved from `ErrorBuilder::debugThrow` to
`EvalState::error`.
2024-01-23 03:08:29 +02:00
|
|
|
|
.pos = state->positions[state->at(*loc)]
|
2024-01-15 17:52:18 +02:00
|
|
|
|
});
|
2006-09-05 00:36:15 +03:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2004-01-30 17:21:42 +02:00
|
|
|
|
%}
|
|
|
|
|
|
|
|
|
|
%union {
|
2013-09-02 17:29:15 +03:00
|
|
|
|
// !!! We're probably leaking stuff here.
|
2010-04-12 21:30:11 +03:00
|
|
|
|
nix::Expr * e;
|
|
|
|
|
nix::ExprList * list;
|
|
|
|
|
nix::ExprAttrs * attrs;
|
2024-01-15 17:52:18 +02:00
|
|
|
|
nix::Formals * formals;
|
2010-04-12 21:30:11 +03:00
|
|
|
|
nix::Formal * formal;
|
2013-08-19 13:35:03 +03:00
|
|
|
|
nix::NixInt n;
|
2016-01-05 01:40:40 +02:00
|
|
|
|
nix::NixFloat nf;
|
2024-01-15 17:52:18 +02:00
|
|
|
|
nix::StringToken id; // !!! -> Symbol
|
|
|
|
|
nix::StringToken path;
|
|
|
|
|
nix::StringToken uri;
|
|
|
|
|
nix::StringToken str;
|
2014-01-01 01:56:26 +02:00
|
|
|
|
std::vector<nix::AttrName> * attrNames;
|
2022-05-25 16:49:41 +03:00
|
|
|
|
std::vector<std::pair<nix::PosIdx, nix::Expr *>> * string_parts;
|
2024-01-15 17:52:18 +02:00
|
|
|
|
std::vector<std::pair<nix::PosIdx, std::variant<nix::Expr *, nix::StringToken>>> * ind_string_parts;
|
2004-01-30 17:21:42 +02:00
|
|
|
|
}
|
|
|
|
|
|
2010-04-12 21:30:11 +03:00
|
|
|
|
%type <e> start expr expr_function expr_if expr_op
|
2020-03-03 16:32:20 +02:00
|
|
|
|
%type <e> expr_select expr_simple expr_app
|
2010-04-12 21:30:11 +03:00
|
|
|
|
%type <list> expr_list
|
|
|
|
|
%type <attrs> binds
|
2008-08-14 17:00:44 +03:00
|
|
|
|
%type <formals> formals
|
2010-04-12 21:30:11 +03:00
|
|
|
|
%type <formal> formal
|
2014-01-01 01:56:26 +02:00
|
|
|
|
%type <attrNames> attrs attrpath
|
2022-01-19 14:39:42 +02:00
|
|
|
|
%type <string_parts> string_parts_interpolated
|
|
|
|
|
%type <ind_string_parts> ind_string_parts
|
2021-07-29 19:03:07 +03:00
|
|
|
|
%type <e> path_start string_parts string_attr
|
2011-07-13 15:19:57 +03:00
|
|
|
|
%type <id> attr
|
2023-06-23 08:35:41 +03:00
|
|
|
|
%token <id> ID
|
2022-01-19 14:39:42 +02:00
|
|
|
|
%token <str> STR IND_STR
|
2024-01-13 02:46:48 +02:00
|
|
|
|
%token <n> INT_LIT
|
|
|
|
|
%token <nf> FLOAT_LIT
|
2021-07-29 19:03:07 +03:00
|
|
|
|
%token <path> PATH HPATH SPATH PATH_END
|
2010-04-12 21:30:11 +03:00
|
|
|
|
%token <uri> URI
|
2024-01-13 02:46:48 +02:00
|
|
|
|
%token IF THEN ELSE ASSERT WITH LET IN_KW REC INHERIT EQ NEQ AND OR IMPL OR_KW
|
2006-05-01 17:01:47 +03:00
|
|
|
|
%token DOLLAR_CURLY /* == ${ */
|
2007-11-30 18:48:45 +02:00
|
|
|
|
%token IND_STRING_OPEN IND_STRING_CLOSE
|
2008-08-14 17:00:44 +03:00
|
|
|
|
%token ELLIPSIS
|
2004-01-30 17:21:42 +02:00
|
|
|
|
|
2018-07-23 10:28:48 +03:00
|
|
|
|
%right IMPL
|
2004-01-30 17:21:42 +02:00
|
|
|
|
%left OR
|
|
|
|
|
%left AND
|
|
|
|
|
%nonassoc EQ NEQ
|
2018-07-21 18:24:51 +03:00
|
|
|
|
%nonassoc '<' '>' LEQ GEQ
|
2004-02-04 18:49:51 +02:00
|
|
|
|
%right UPDATE
|
2013-08-02 18:35:59 +03:00
|
|
|
|
%left NOT
|
2013-08-02 19:03:02 +03:00
|
|
|
|
%left '+' '-'
|
|
|
|
|
%left '*' '/'
|
2005-09-14 14:41:59 +03:00
|
|
|
|
%right CONCAT
|
2004-03-29 00:15:01 +03:00
|
|
|
|
%nonassoc '?'
|
2013-08-02 18:35:59 +03:00
|
|
|
|
%nonassoc NEGATE
|
2004-01-30 17:21:42 +02:00
|
|
|
|
|
|
|
|
|
%%
|
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
start: expr { state->result = $1; };
|
2004-01-30 17:21:42 +02:00
|
|
|
|
|
|
|
|
|
expr: expr_function;
|
|
|
|
|
|
|
|
|
|
expr_function
|
2010-04-12 21:30:11 +03:00
|
|
|
|
: ID ':' expr_function
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new ExprLambda(CUR_POS, state->symbols.create($1), 0, $3); }
|
2010-04-12 21:30:11 +03:00
|
|
|
|
| '{' formals '}' ':' expr_function
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new ExprLambda(CUR_POS, state->validateFormals($2), $5); }
|
2010-04-12 21:30:11 +03:00
|
|
|
|
| '{' formals '}' '@' ID ':' expr_function
|
2022-01-19 17:49:02 +02:00
|
|
|
|
{
|
2024-01-15 17:52:18 +02:00
|
|
|
|
auto arg = state->symbols.create($5);
|
|
|
|
|
$$ = new ExprLambda(CUR_POS, arg, state->validateFormals($2, CUR_POS, arg), $7);
|
2022-01-19 17:49:02 +02:00
|
|
|
|
}
|
2010-04-12 21:30:11 +03:00
|
|
|
|
| ID '@' '{' formals '}' ':' expr_function
|
2022-01-19 17:49:02 +02:00
|
|
|
|
{
|
2024-01-15 17:52:18 +02:00
|
|
|
|
auto arg = state->symbols.create($1);
|
|
|
|
|
$$ = new ExprLambda(CUR_POS, arg, state->validateFormals($4, CUR_POS, arg), $7);
|
2022-01-19 17:49:02 +02:00
|
|
|
|
}
|
2010-04-13 00:21:24 +03:00
|
|
|
|
| ASSERT expr ';' expr_function
|
|
|
|
|
{ $$ = new ExprAssert(CUR_POS, $2, $4); }
|
2004-10-25 19:54:56 +03:00
|
|
|
|
| WITH expr ';' expr_function
|
2010-04-12 21:30:11 +03:00
|
|
|
|
{ $$ = new ExprWith(CUR_POS, $2, $4); }
|
2024-01-13 02:46:48 +02:00
|
|
|
|
| LET binds IN_KW expr_function
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
{ if (!$2->dynamicAttrs.empty())
|
2020-06-15 15:06:58 +03:00
|
|
|
|
throw ParseError({
|
2024-02-04 06:35:19 +02:00
|
|
|
|
.msg = HintFmt("dynamic attributes not allowed in let"),
|
libexpr: Support structured error classes
While preparing PRs like #9753, I've had to change error messages in
dozens of code paths. It would be nice if instead of
EvalError("expected 'boolean' but found '%1%'", showType(v))
we could write
TypeError(v, "boolean")
or similar. Then, changing the error message could be a mechanical
refactor with the compiler pointing out places the constructor needs to
be changed, rather than the error-prone process of grepping through the
codebase. Structured errors would also help prevent the "same" error
from having multiple slightly different messages, and could be a first
step towards error codes / an error index.
This PR reworks the exception infrastructure in `libexpr` to
support exception types with different constructor signatures than
`BaseError`. Actually refactoring the exceptions to use structured data
will come in a future PR (this one is big enough already, as it has to
touch every exception in `libexpr`).
The core design is in `eval-error.hh`. Generally, errors like this:
state.error("'%s' is not a string", getAttrPathStr())
.debugThrow<TypeError>()
are transformed like this:
state.error<TypeError>("'%s' is not a string", getAttrPathStr())
.debugThrow()
The type annotation has moved from `ErrorBuilder::debugThrow` to
`EvalState::error`.
2024-01-23 03:08:29 +02:00
|
|
|
|
.pos = state->positions[CUR_POS]
|
2020-06-15 15:06:58 +03:00
|
|
|
|
});
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
$$ = new ExprLet($2, $4);
|
|
|
|
|
}
|
2004-02-19 15:11:12 +02:00
|
|
|
|
| expr_if
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
expr_if
|
2022-10-20 14:55:15 +03:00
|
|
|
|
: IF expr THEN expr ELSE expr { $$ = new ExprIf(CUR_POS, $2, $4, $6); }
|
2004-01-30 17:21:42 +02:00
|
|
|
|
| expr_op
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
expr_op
|
2013-08-02 18:35:59 +03:00
|
|
|
|
: '!' expr_op %prec NOT { $$ = new ExprOpNot($2); }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| '-' expr_op %prec NEGATE { $$ = new ExprCall(CUR_POS, new ExprVar(state->s.sub), {new ExprInt(0), $2}); }
|
2010-04-13 00:21:24 +03:00
|
|
|
|
| expr_op EQ expr_op { $$ = new ExprOpEq($1, $3); }
|
2010-04-12 21:30:11 +03:00
|
|
|
|
| expr_op NEQ expr_op { $$ = new ExprOpNEq($1, $3); }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| expr_op '<' expr_op { $$ = new ExprCall(state->at(@2), new ExprVar(state->s.lessThan), {$1, $3}); }
|
|
|
|
|
| expr_op LEQ expr_op { $$ = new ExprOpNot(new ExprCall(state->at(@2), new ExprVar(state->s.lessThan), {$3, $1})); }
|
|
|
|
|
| expr_op '>' expr_op { $$ = new ExprCall(state->at(@2), new ExprVar(state->s.lessThan), {$3, $1}); }
|
|
|
|
|
| expr_op GEQ expr_op { $$ = new ExprOpNot(new ExprCall(state->at(@2), new ExprVar(state->s.lessThan), {$1, $3})); }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| expr_op AND expr_op { $$ = new ExprOpAnd(state->at(@2), $1, $3); }
|
|
|
|
|
| expr_op OR expr_op { $$ = new ExprOpOr(state->at(@2), $1, $3); }
|
|
|
|
|
| expr_op IMPL expr_op { $$ = new ExprOpImpl(state->at(@2), $1, $3); }
|
|
|
|
|
| expr_op UPDATE expr_op { $$ = new ExprOpUpdate(state->at(@2), $1, $3); }
|
2023-02-11 01:37:23 +02:00
|
|
|
|
| expr_op '?' attrpath { $$ = new ExprOpHasAttr($1, std::move(*$3)); delete $3; }
|
2010-04-13 00:21:24 +03:00
|
|
|
|
| expr_op '+' expr_op
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new ExprConcatStrings(state->at(@2), false, new std::vector<std::pair<PosIdx, Expr *> >({{state->at(@1), $1}, {state->at(@3), $3}})); }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| expr_op '-' expr_op { $$ = new ExprCall(state->at(@2), new ExprVar(state->s.sub), {$1, $3}); }
|
|
|
|
|
| expr_op '*' expr_op { $$ = new ExprCall(state->at(@2), new ExprVar(state->s.mul), {$1, $3}); }
|
|
|
|
|
| expr_op '/' expr_op { $$ = new ExprCall(state->at(@2), new ExprVar(state->s.div), {$1, $3}); }
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| expr_op CONCAT expr_op { $$ = new ExprOpConcatLists(state->at(@2), $1, $3); }
|
2020-03-03 16:32:20 +02:00
|
|
|
|
| expr_app
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
expr_app
|
2020-02-24 02:32:01 +02:00
|
|
|
|
: expr_app expr_select {
|
2020-03-03 16:32:20 +02:00
|
|
|
|
if (auto e2 = dynamic_cast<ExprCall *>($1)) {
|
|
|
|
|
e2->args.push_back($2);
|
2020-02-24 02:32:01 +02:00
|
|
|
|
$$ = $1;
|
2020-03-03 16:32:20 +02:00
|
|
|
|
} else
|
|
|
|
|
$$ = new ExprCall(CUR_POS, $1, {$2});
|
2020-02-24 02:32:01 +02:00
|
|
|
|
}
|
2020-03-03 16:32:20 +02:00
|
|
|
|
| expr_select
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
expr_select
|
2011-07-06 15:28:57 +03:00
|
|
|
|
: expr_simple '.' attrpath
|
2023-02-11 01:37:23 +02:00
|
|
|
|
{ $$ = new ExprSelect(CUR_POS, $1, std::move(*$3), nullptr); delete $3; }
|
2011-07-13 15:19:57 +03:00
|
|
|
|
| expr_simple '.' attrpath OR_KW expr_select
|
2023-02-11 01:37:23 +02:00
|
|
|
|
{ $$ = new ExprSelect(CUR_POS, $1, std::move(*$3), $5); delete $3; }
|
2011-07-13 15:19:57 +03:00
|
|
|
|
| /* Backwards compatibility: because Nixpkgs has a rarely used
|
2016-11-26 01:37:43 +02:00
|
|
|
|
function named ‘or’, allow stuff like ‘map or [...]’. */
|
2011-07-13 15:19:57 +03:00
|
|
|
|
expr_simple OR_KW
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new ExprCall(CUR_POS, $1, {new ExprVar(CUR_POS, state->s.or_)}); }
|
2023-02-12 06:45:25 +02:00
|
|
|
|
| expr_simple
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
expr_simple
|
2013-11-18 21:14:54 +02:00
|
|
|
|
: ID {
|
2022-01-24 16:18:18 +02:00
|
|
|
|
std::string_view s = "__curPos";
|
2022-01-25 11:49:27 +02:00
|
|
|
|
if ($1.l == s.size() && strncmp($1.p, s.data(), s.size()) == 0)
|
2013-11-18 21:14:54 +02:00
|
|
|
|
$$ = new ExprPos(CUR_POS);
|
|
|
|
|
else
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$ = new ExprVar(CUR_POS, state->symbols.create($1));
|
2013-11-18 21:14:54 +02:00
|
|
|
|
}
|
2024-01-13 02:46:48 +02:00
|
|
|
|
| INT_LIT { $$ = new ExprInt($1); }
|
|
|
|
|
| FLOAT_LIT { $$ = new ExprFloat($1); }
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
| '"' string_parts '"' { $$ = $2; }
|
2007-11-30 18:48:45 +02:00
|
|
|
|
| IND_STRING_OPEN ind_string_parts IND_STRING_CLOSE {
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$ = state->stripIndentation(CUR_POS, std::move(*$2));
|
2023-02-11 01:37:23 +02:00
|
|
|
|
delete $2;
|
2007-11-30 18:48:45 +02:00
|
|
|
|
}
|
2023-02-12 06:45:25 +02:00
|
|
|
|
| path_start PATH_END
|
2021-07-29 19:03:07 +03:00
|
|
|
|
| path_start string_parts_interpolated PATH_END {
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$2->insert($2->begin(), {state->at(@1), $1});
|
2021-07-29 19:03:07 +03:00
|
|
|
|
$$ = new ExprConcatStrings(CUR_POS, false, $2);
|
|
|
|
|
}
|
2011-08-06 19:05:24 +03:00
|
|
|
|
| SPATH {
|
2022-02-25 17:00:00 +02:00
|
|
|
|
std::string path($1.p + 1, $1.l - 2);
|
2020-02-24 02:32:01 +02:00
|
|
|
|
$$ = new ExprCall(CUR_POS,
|
2024-01-15 17:52:18 +02:00
|
|
|
|
new ExprVar(state->s.findFile),
|
|
|
|
|
{new ExprVar(state->s.nixPath),
|
2023-02-11 01:34:31 +02:00
|
|
|
|
new ExprString(std::move(path))});
|
2011-08-06 19:05:24 +03:00
|
|
|
|
}
|
2019-11-26 20:48:34 +02:00
|
|
|
|
| URI {
|
2023-03-17 16:33:48 +02:00
|
|
|
|
static bool noURLLiterals = experimentalFeatureSettings.isEnabled(Xp::NoUrlLiterals);
|
2019-11-26 20:48:34 +02:00
|
|
|
|
if (noURLLiterals)
|
2020-06-15 15:06:58 +03:00
|
|
|
|
throw ParseError({
|
2024-02-04 06:35:19 +02:00
|
|
|
|
.msg = HintFmt("URL literals are disabled"),
|
libexpr: Support structured error classes
While preparing PRs like #9753, I've had to change error messages in
dozens of code paths. It would be nice if instead of
EvalError("expected 'boolean' but found '%1%'", showType(v))
we could write
TypeError(v, "boolean")
or similar. Then, changing the error message could be a mechanical
refactor with the compiler pointing out places the constructor needs to
be changed, rather than the error-prone process of grepping through the
codebase. Structured errors would also help prevent the "same" error
from having multiple slightly different messages, and could be a first
step towards error codes / an error index.
This PR reworks the exception infrastructure in `libexpr` to
support exception types with different constructor signatures than
`BaseError`. Actually refactoring the exceptions to use structured data
will come in a future PR (this one is big enough already, as it has to
touch every exception in `libexpr`).
The core design is in `eval-error.hh`. Generally, errors like this:
state.error("'%s' is not a string", getAttrPathStr())
.debugThrow<TypeError>()
are transformed like this:
state.error<TypeError>("'%s' is not a string", getAttrPathStr())
.debugThrow()
The type annotation has moved from `ErrorBuilder::debugThrow` to
`EvalState::error`.
2024-01-23 03:08:29 +02:00
|
|
|
|
.pos = state->positions[CUR_POS]
|
2020-06-15 15:06:58 +03:00
|
|
|
|
});
|
2022-02-25 17:00:00 +02:00
|
|
|
|
$$ = new ExprString(std::string($1));
|
2019-11-26 20:48:34 +02:00
|
|
|
|
}
|
2004-01-30 17:21:42 +02:00
|
|
|
|
| '(' expr ')' { $$ = $2; }
|
2004-02-02 23:39:33 +02:00
|
|
|
|
/* Let expressions `let {..., body = ...}' are just desugared
|
2010-04-13 00:21:24 +03:00
|
|
|
|
into `(rec {..., body = ...}).body'. */
|
2004-02-02 23:39:33 +02:00
|
|
|
|
| LET '{' binds '}'
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $3->recursive = true; $$ = new ExprSelect(noPos, $3, state->s.body); }
|
2004-02-02 23:39:33 +02:00
|
|
|
|
| REC '{' binds '}'
|
2010-04-13 02:33:23 +03:00
|
|
|
|
{ $3->recursive = true; $$ = $3; }
|
2004-02-02 23:39:33 +02:00
|
|
|
|
| '{' binds '}'
|
2010-04-13 02:33:23 +03:00
|
|
|
|
{ $$ = $2; }
|
2010-04-12 21:30:11 +03:00
|
|
|
|
| '[' expr_list ']' { $$ = $2; }
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
2006-05-01 17:01:47 +03:00
|
|
|
|
string_parts
|
2022-02-25 17:00:00 +02:00
|
|
|
|
: STR { $$ = new ExprString(std::string($1)); }
|
2014-04-04 23:19:33 +03:00
|
|
|
|
| string_parts_interpolated { $$ = new ExprConcatStrings(CUR_POS, true, $1); }
|
2022-01-19 15:31:30 +02:00
|
|
|
|
| { $$ = new ExprString(""); }
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
string_parts_interpolated
|
2022-01-19 14:39:42 +02:00
|
|
|
|
: string_parts_interpolated STR
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = $1; $1->emplace_back(state->at(@2), new ExprString(std::string($2))); }
|
|
|
|
|
| string_parts_interpolated DOLLAR_CURLY expr '}' { $$ = $1; $1->emplace_back(state->at(@2), $3); }
|
|
|
|
|
| DOLLAR_CURLY expr '}' { $$ = new std::vector<std::pair<PosIdx, Expr *>>; $$->emplace_back(state->at(@1), $2); }
|
2015-07-02 19:39:02 +03:00
|
|
|
|
| STR DOLLAR_CURLY expr '}' {
|
2022-05-25 16:49:41 +03:00
|
|
|
|
$$ = new std::vector<std::pair<PosIdx, Expr *>>;
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$->emplace_back(state->at(@1), new ExprString(std::string($1)));
|
|
|
|
|
$$->emplace_back(state->at(@2), $3);
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
}
|
2006-05-01 17:01:47 +03:00
|
|
|
|
;
|
|
|
|
|
|
2021-07-29 19:03:07 +03:00
|
|
|
|
path_start
|
|
|
|
|
: PATH {
|
2024-01-15 17:52:18 +02:00
|
|
|
|
Path path(absPath({$1.p, $1.l}, state->basePath.path.abs()));
|
2021-07-29 19:03:07 +03:00
|
|
|
|
/* add back in the trailing '/' to the first segment */
|
don't strdup tokens in the lexer
every stringy token the lexer returns is turned into a Symbol and not
used further, so we don't have to strdup. using a string_view is
sufficient, but due to limitations of the current parser we have to use
a POD type that holds the same information.
gives ~2% on system build, 6% on search, 8% on parsing alone
# before
Benchmark 1: nix search --offline nixpkgs hello
Time (mean ± σ): 610.6 ms ± 2.4 ms [User: 602.5 ms, System: 7.8 ms]
Range (min … max): 606.6 ms … 617.3 ms 50 runs
Benchmark 2: nix eval -f hackage-packages.nix
Time (mean ± σ): 430.1 ms ± 1.4 ms [User: 393.1 ms, System: 36.7 ms]
Range (min … max): 428.2 ms … 434.2 ms 50 runs
Benchmark 3: nix eval --raw --impure --expr 'with import <nixpkgs/nixos> {}; system'
Time (mean ± σ): 3.032 s ± 0.005 s [User: 2.808 s, System: 0.223 s]
Range (min … max): 3.023 s … 3.041 s 50 runs
# after
Benchmark 1: nix search --offline nixpkgs hello
Time (mean ± σ): 574.7 ms ± 2.8 ms [User: 566.3 ms, System: 8.0 ms]
Range (min … max): 569.2 ms … 580.7 ms 50 runs
Benchmark 2: nix eval -f hackage-packages.nix
Time (mean ± σ): 394.4 ms ± 0.8 ms [User: 361.8 ms, System: 32.3 ms]
Range (min … max): 392.7 ms … 395.7 ms 50 runs
Benchmark 3: nix eval --raw --impure --expr 'with import <nixpkgs/nixos> {}; system'
Time (mean ± σ): 2.976 s ± 0.005 s [User: 2.757 s, System: 0.218 s]
Range (min … max): 2.966 s … 2.990 s 50 runs
2021-12-21 10:17:31 +02:00
|
|
|
|
if ($1.p[$1.l-1] == '/' && $1.l > 1)
|
2021-07-29 19:03:07 +03:00
|
|
|
|
path += "/";
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$ = new ExprPath(ref<InputAccessor>(state->rootFS), std::move(path));
|
2021-07-29 19:03:07 +03:00
|
|
|
|
}
|
|
|
|
|
| HPATH {
|
2022-06-21 15:08:18 +03:00
|
|
|
|
if (evalSettings.pureEval) {
|
|
|
|
|
throw Error(
|
|
|
|
|
"the path '%s' can not be resolved in pure mode",
|
|
|
|
|
std::string_view($1.p, $1.l)
|
|
|
|
|
);
|
|
|
|
|
}
|
2022-02-25 17:00:00 +02:00
|
|
|
|
Path path(getHome() + std::string($1.p + 1, $1.l - 1));
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$ = new ExprPath(ref<InputAccessor>(state->rootFS), std::move(path));
|
2021-07-29 19:03:07 +03:00
|
|
|
|
}
|
|
|
|
|
;
|
|
|
|
|
|
2007-11-30 18:48:45 +02:00
|
|
|
|
ind_string_parts
|
2024-01-15 17:52:18 +02:00
|
|
|
|
: ind_string_parts IND_STR { $$ = $1; $1->emplace_back(state->at(@2), $2); }
|
|
|
|
|
| ind_string_parts DOLLAR_CURLY expr '}' { $$ = $1; $1->emplace_back(state->at(@2), $3); }
|
2022-05-25 16:49:41 +03:00
|
|
|
|
| { $$ = new std::vector<std::pair<PosIdx, std::variant<Expr *, StringToken>>>; }
|
2007-11-30 18:48:45 +02:00
|
|
|
|
;
|
|
|
|
|
|
2004-01-30 17:21:42 +02:00
|
|
|
|
binds
|
2024-01-15 17:52:18 +02:00
|
|
|
|
: binds attrpath '=' expr ';' { $$ = $1; state->addAttr($$, std::move(*$2), $4, state->at(@2)); delete $2; }
|
2011-07-13 15:19:57 +03:00
|
|
|
|
| binds INHERIT attrs ';'
|
2010-04-12 21:30:11 +03:00
|
|
|
|
{ $$ = $1;
|
2015-07-17 20:24:28 +03:00
|
|
|
|
for (auto & i : *$3) {
|
|
|
|
|
if ($$->attrs.find(i.symbol) != $$->attrs.end())
|
2024-01-15 17:52:18 +02:00
|
|
|
|
state->dupAttr(i.symbol, state->at(@3), $$->attrs[i.symbol].pos);
|
|
|
|
|
auto pos = state->at(@3);
|
2024-01-27 17:33:34 +02:00
|
|
|
|
$$->attrs.emplace(
|
|
|
|
|
i.symbol,
|
|
|
|
|
ExprAttrs::AttrDef(new ExprVar(CUR_POS, i.symbol), pos, ExprAttrs::AttrDef::Kind::Inherited));
|
2010-04-22 14:02:24 +03:00
|
|
|
|
}
|
2023-02-11 01:37:23 +02:00
|
|
|
|
delete $3;
|
2010-04-12 21:30:11 +03:00
|
|
|
|
}
|
2011-07-13 15:19:57 +03:00
|
|
|
|
| binds INHERIT '(' expr ')' attrs ';'
|
2010-04-12 21:30:11 +03:00
|
|
|
|
{ $$ = $1;
|
|
|
|
|
/* !!! Should ensure sharing of the expression in $4. */
|
2015-07-17 20:24:28 +03:00
|
|
|
|
for (auto & i : *$6) {
|
|
|
|
|
if ($$->attrs.find(i.symbol) != $$->attrs.end())
|
2024-01-15 17:52:18 +02:00
|
|
|
|
state->dupAttr(i.symbol, state->at(@6), $$->attrs[i.symbol].pos);
|
2024-01-27 17:33:34 +02:00
|
|
|
|
$$->attrs.emplace(
|
|
|
|
|
i.symbol,
|
|
|
|
|
ExprAttrs::AttrDef(
|
|
|
|
|
new ExprSelect(CUR_POS, $4, i.symbol),
|
|
|
|
|
state->at(@6),
|
|
|
|
|
ExprAttrs::AttrDef::Kind::InheritedFrom));
|
2011-07-13 15:19:57 +03:00
|
|
|
|
}
|
2023-02-11 01:37:23 +02:00
|
|
|
|
delete $6;
|
2011-07-13 15:19:57 +03:00
|
|
|
|
}
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| { $$ = new ExprAttrs(state->at(@0)); }
|
2004-02-04 19:23:26 +02:00
|
|
|
|
;
|
|
|
|
|
|
2011-07-13 15:19:57 +03:00
|
|
|
|
attrs
|
2024-01-15 17:52:18 +02:00
|
|
|
|
: attrs attr { $$ = $1; $1->push_back(AttrName(state->symbols.create($2))); }
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
| attrs string_attr
|
|
|
|
|
{ $$ = $1;
|
2014-10-05 02:04:58 +03:00
|
|
|
|
ExprString * str = dynamic_cast<ExprString *>($2);
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
if (str) {
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$->push_back(AttrName(state->symbols.create(str->s)));
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
delete str;
|
|
|
|
|
} else
|
2020-06-15 15:06:58 +03:00
|
|
|
|
throw ParseError({
|
2024-02-04 06:35:19 +02:00
|
|
|
|
.msg = HintFmt("dynamic attributes not allowed in inherit"),
|
libexpr: Support structured error classes
While preparing PRs like #9753, I've had to change error messages in
dozens of code paths. It would be nice if instead of
EvalError("expected 'boolean' but found '%1%'", showType(v))
we could write
TypeError(v, "boolean")
or similar. Then, changing the error message could be a mechanical
refactor with the compiler pointing out places the constructor needs to
be changed, rather than the error-prone process of grepping through the
codebase. Structured errors would also help prevent the "same" error
from having multiple slightly different messages, and could be a first
step towards error codes / an error index.
This PR reworks the exception infrastructure in `libexpr` to
support exception types with different constructor signatures than
`BaseError`. Actually refactoring the exceptions to use structured data
will come in a future PR (this one is big enough already, as it has to
touch every exception in `libexpr`).
The core design is in `eval-error.hh`. Generally, errors like this:
state.error("'%s' is not a string", getAttrPathStr())
.debugThrow<TypeError>()
are transformed like this:
state.error<TypeError>("'%s' is not a string", getAttrPathStr())
.debugThrow()
The type annotation has moved from `ErrorBuilder::debugThrow` to
`EvalState::error`.
2024-01-23 03:08:29 +02:00
|
|
|
|
.pos = state->positions[state->at(@2)]
|
2020-06-15 15:06:58 +03:00
|
|
|
|
});
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
}
|
2014-01-01 01:56:26 +02:00
|
|
|
|
| { $$ = new AttrPath; }
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
2009-05-15 15:35:23 +03:00
|
|
|
|
attrpath
|
2024-01-15 17:52:18 +02:00
|
|
|
|
: attrpath '.' attr { $$ = $1; $1->push_back(AttrName(state->symbols.create($3))); }
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
| attrpath '.' string_attr
|
|
|
|
|
{ $$ = $1;
|
2014-10-05 02:04:58 +03:00
|
|
|
|
ExprString * str = dynamic_cast<ExprString *>($3);
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
if (str) {
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$->push_back(AttrName(state->symbols.create(str->s)));
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
delete str;
|
|
|
|
|
} else
|
2014-10-05 02:04:58 +03:00
|
|
|
|
$$->push_back(AttrName($3));
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
}
|
2024-01-15 17:52:18 +02:00
|
|
|
|
| attr { $$ = new std::vector<AttrName>; $$->push_back(AttrName(state->symbols.create($1))); }
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
| string_attr
|
2022-02-21 17:32:34 +02:00
|
|
|
|
{ $$ = new std::vector<AttrName>;
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
ExprString *str = dynamic_cast<ExprString *>($1);
|
|
|
|
|
if (str) {
|
2024-01-15 17:52:18 +02:00
|
|
|
|
$$->push_back(AttrName(state->symbols.create(str->s)));
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
delete str;
|
|
|
|
|
} else
|
2014-10-05 02:04:58 +03:00
|
|
|
|
$$->push_back(AttrName($1));
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
}
|
2011-07-13 15:19:57 +03:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
attr
|
2023-02-12 06:45:25 +02:00
|
|
|
|
: ID
|
don't strdup tokens in the lexer
every stringy token the lexer returns is turned into a Symbol and not
used further, so we don't have to strdup. using a string_view is
sufficient, but due to limitations of the current parser we have to use
a POD type that holds the same information.
gives ~2% on system build, 6% on search, 8% on parsing alone
# before
Benchmark 1: nix search --offline nixpkgs hello
Time (mean ± σ): 610.6 ms ± 2.4 ms [User: 602.5 ms, System: 7.8 ms]
Range (min … max): 606.6 ms … 617.3 ms 50 runs
Benchmark 2: nix eval -f hackage-packages.nix
Time (mean ± σ): 430.1 ms ± 1.4 ms [User: 393.1 ms, System: 36.7 ms]
Range (min … max): 428.2 ms … 434.2 ms 50 runs
Benchmark 3: nix eval --raw --impure --expr 'with import <nixpkgs/nixos> {}; system'
Time (mean ± σ): 3.032 s ± 0.005 s [User: 2.808 s, System: 0.223 s]
Range (min … max): 3.023 s … 3.041 s 50 runs
# after
Benchmark 1: nix search --offline nixpkgs hello
Time (mean ± σ): 574.7 ms ± 2.8 ms [User: 566.3 ms, System: 8.0 ms]
Range (min … max): 569.2 ms … 580.7 ms 50 runs
Benchmark 2: nix eval -f hackage-packages.nix
Time (mean ± σ): 394.4 ms ± 0.8 ms [User: 361.8 ms, System: 32.3 ms]
Range (min … max): 392.7 ms … 395.7 ms 50 runs
Benchmark 3: nix eval --raw --impure --expr 'with import <nixpkgs/nixos> {}; system'
Time (mean ± σ): 2.976 s ± 0.005 s [User: 2.757 s, System: 0.218 s]
Range (min … max): 2.966 s … 2.990 s 50 runs
2021-12-21 10:17:31 +02:00
|
|
|
|
| OR_KW { $$ = {"or", 2}; }
|
Dynamic attrs
This adds new syntax for attribute names:
* attrs."${name}" => getAttr name attrs
* attrs ? "${name}" => isAttrs attrs && hasAttr attrs name
* attrs."${name}" or def => if attrs ? "${name}" then attrs."${name}" else def
* { "${name}" = value; } => listToAttrs [{ inherit name value; }]
Of course, it's a bit more complicated than that. The attribute chains
can be arbitrarily long and contain combinations of static and dynamic
parts (e.g. attrs."${foo}".bar."${baz}" or qux), which is relatively
straightforward for the getAttrs/hasAttrs cases but is more complex for
the listToAttrs case due to rules about duplicate attribute definitions.
For attribute sets with dynamic attribute names, duplicate static
attributes are detected at parse time while duplicate dynamic attributes
are detected when the attribute set is forced. So, for example, { a =
null; a.b = null; "${"c"}" = true; } will be a parse-time error, while
{ a = {}; "${"a"}".b = null; c = true; } will be an eval-time error
(technically that case could theoretically be detected at parse time,
but the general case would require full evaluation). Moreover, duplicate
dynamic attributes are not allowed even in cases where they would be
with static attributes ({ a.b.d = true; a.b.c = false; } is legal, but {
a."${"b"}".d = true; a."${"b"}".c = false; } is not). This restriction
might be relaxed in the future in cases where the static variant would
not be an error, but it is not obvious that that is desirable.
Finally, recursive attribute sets with dynamic attributes have the
static attributes in scope but not the dynamic ones. So rec { a = true;
"${"b"}" = a; } is equivalent to { a = true; b = true; } but rec {
"${"a"}" = true; b = a; } would be an error or use a from the
surrounding scope if it exists.
Note that the getAttr, getAttr or default, and hasAttr are all
implemented purely in the parser as syntactic sugar, while attribute
sets with dynamic attribute names required changes to the AST to be
implemented cleanly.
This is an alternative solution to and closes #167
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-21 06:25:30 +03:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
string_attr
|
|
|
|
|
: '"' string_parts '"' { $$ = $2; }
|
2014-10-05 02:04:58 +03:00
|
|
|
|
| DOLLAR_CURLY expr '}' { $$ = $2; }
|
2009-05-15 15:35:23 +03:00
|
|
|
|
;
|
|
|
|
|
|
2004-01-30 17:21:42 +02:00
|
|
|
|
expr_list
|
2010-04-12 21:30:11 +03:00
|
|
|
|
: expr_list expr_select { $$ = $1; $1->elems.push_back($2); /* !!! dangerous */ }
|
|
|
|
|
| { $$ = new ExprList; }
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
formals
|
2010-04-12 21:30:11 +03:00
|
|
|
|
: formal ',' formals
|
2023-02-11 01:37:23 +02:00
|
|
|
|
{ $$ = $3; $$->formals.emplace_back(*$1); delete $1; }
|
2008-08-14 17:00:44 +03:00
|
|
|
|
| formal
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new Formals; $$->formals.emplace_back(*$1); $$->ellipsis = false; delete $1; }
|
2008-08-14 17:00:44 +03:00
|
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new Formals; $$->ellipsis = false; }
|
2008-08-14 17:00:44 +03:00
|
|
|
|
| ELLIPSIS
|
2024-01-15 17:52:18 +02:00
|
|
|
|
{ $$ = new Formals; $$->ellipsis = true; }
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
formal
|
2024-01-15 17:52:18 +02:00
|
|
|
|
: ID { $$ = new Formal{CUR_POS, state->symbols.create($1), 0}; }
|
|
|
|
|
| ID '?' expr { $$ = new Formal{CUR_POS, state->symbols.create($1), $3}; }
|
2004-01-30 17:21:42 +02:00
|
|
|
|
;
|
2013-09-02 17:29:15 +03:00
|
|
|
|
|
2004-01-30 17:21:42 +02:00
|
|
|
|
%%
|
2006-09-05 00:36:15 +03:00
|
|
|
|
|
2016-04-29 22:04:40 +03:00
|
|
|
|
#include "eval.hh"
|
2010-04-13 15:25:42 +03:00
|
|
|
|
|
2006-09-05 00:36:15 +03:00
|
|
|
|
|
|
|
|
|
namespace nix {
|
2013-09-02 17:29:15 +03:00
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
Expr * parseExprFromBuf(
|
2022-12-13 01:48:04 +02:00
|
|
|
|
char * text,
|
|
|
|
|
size_t length,
|
|
|
|
|
Pos::Origin origin,
|
2023-04-06 14:15:50 +03:00
|
|
|
|
const SourcePath & basePath,
|
2024-01-15 17:52:18 +02:00
|
|
|
|
SymbolTable & symbols,
|
|
|
|
|
PosTable & positions,
|
2024-01-15 17:52:18 +02:00
|
|
|
|
const ref<InputAccessor> rootFS,
|
|
|
|
|
const Expr::AstSymbols & astSymbols)
|
2006-09-05 00:36:15 +03:00
|
|
|
|
{
|
|
|
|
|
yyscan_t scanner;
|
2024-01-15 17:52:18 +02:00
|
|
|
|
ParserState state {
|
2022-12-13 01:48:04 +02:00
|
|
|
|
.symbols = symbols,
|
2024-01-15 17:52:18 +02:00
|
|
|
|
.positions = positions,
|
2023-07-10 07:02:29 +03:00
|
|
|
|
.basePath = basePath,
|
2022-12-13 01:48:04 +02:00
|
|
|
|
.origin = {origin},
|
2024-01-15 17:52:18 +02:00
|
|
|
|
.rootFS = rootFS,
|
2024-01-15 17:52:18 +02:00
|
|
|
|
.s = astSymbols,
|
2022-12-13 01:48:04 +02:00
|
|
|
|
};
|
2006-09-05 00:36:15 +03:00
|
|
|
|
|
|
|
|
|
yylex_init(&scanner);
|
2024-01-15 17:52:18 +02:00
|
|
|
|
Finally _destroy([&] { yylex_destroy(scanner); });
|
2013-09-02 17:29:15 +03:00
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
yy_scan_buffer(text, length, scanner);
|
2024-01-15 17:52:18 +02:00
|
|
|
|
yyparse(scanner, &state);
|
2006-09-05 00:36:15 +03:00
|
|
|
|
|
2024-01-15 17:52:18 +02:00
|
|
|
|
return state.result;
|
2006-09-05 00:36:15 +03:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
}
|