diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-10-05 21:21:48 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-10-05 21:21:48 -0700 |
| commit | ec5e0d13b621ef80d30f27b7cdd6edfda34195c8 (patch) | |
| tree | 470ac853a027fe6b3409c22f0ba052c1b918064b /mu.vim | |
| parent | 255c2293e52d5c273b77aec1a0470a24304a1c2c (diff) | |
| download | mu-ec5e0d13b621ef80d30f27b7cdd6edfda34195c8.tar.gz | |
2252
I can't easily use generic containers without needing some syntax for generic recipes: push:number a:number, l:list:number which would be implemented as: T <- next-type a:T <- next-ingredient etc. Another concern: how to represent map<string, list<number>>? map::address:array:character::list:number where the '::' is just silently turned into ':'. Agh, all this is so baroque. All this while I've been trying to avoid getting into language design. All I want is some lightweight way to avoid security holes and memory corruption. But now it seems like I need facets to control compile-time activities and so on.
Diffstat (limited to 'mu.vim')
| -rw-r--r-- | mu.vim | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mu.vim b/mu.vim index 72255940..fc1053a5 100644 --- a/mu.vim +++ b/mu.vim @@ -54,7 +54,7 @@ syntax match muLiteral %[^ ]\+:offset/\?[^ ,]*% syntax match muLiteral %[^ ]\+:variant/\?[^ ,]*% syntax match muLiteral %[^ ]\+:recipe/\?[^ ,]*% highlight link muLiteral Constant -syntax keyword muKeyword default-space global-space new-default-space local-scope next-ingredient ingredient | highlight link muKeyword Constant +syntax keyword muKeyword default-space global-space new-default-space local-scope next-ingredient ingredient next-type | highlight link muKeyword Constant syntax match muDelimiter "[{}]" | highlight link muDelimiter Delimiter syntax match muAssign " <- \|\<raw\>" | highlight link muAssign SpecialChar |