Nim - This repository contains the Nim compiler, Nim's stdlib, tools, and documentation. (mirror)

	Commit message (Collapse)	Author	Age	Files	Lines
*	compiler refactoring; use typesafe path handing; docgen: render symbols ↵	Andreas Rumpf	2018-09-07	1	-7/+7
\| \| \| \|	between modules
*	fixes #8776	Araq	2018-08-27	1	-10/+11
\|
*	remove more global variables in the Nim compiler	Andreas Rumpf	2018-05-27	1	-1/+1
\|
*	move more global variables into ConfigRef	Andreas Rumpf	2018-05-11	1	-4/+4
\|
*	big refactoring: parser compiles again	Andreas Rumpf	2018-05-10	1	-12/+13
\|
*	fixes #6949	Araq	2017-12-21	1	-6/+18
\|
*	implemented new experimental scriptable import mechanism	Andreas Rumpf	2017-10-01	1	-4/+4
\|
*	Fixed handling of versions with dashes in nimble pkgs (#6335)	Yuriy Glukhov	2017-09-06	1	-9/+20
\|
*	Implement .nimble-link files in the compiler and add tests for them.	Dominik Picheta	2017-09-02	1	-3/+14
\|
*	Add readme to tests. Add fileDir option to testament & create nimble test.	Dominik Picheta	2017-09-02	1	-35/+60
\|
*	fixes #5752	Araq	2017-05-02	1	-11/+30
\|
*	removed compiler internal list implementation (#5371)	Arne Döring	2017-02-22	1	-4/+4
\|
*	remove unused stuff	Jacek Sieka	2016-08-09	1	-12/+0
\|
*	added getOrDefault; bootstrapping works again	Araq	2015-10-13	1	-1/+1
\|
*	compiler: Trim .nim files trailing whitespace	Adam Strzelecki	2015-09-04	1	-3/+3
\| \| \| \|	via OSX: find . -name '*.nim' -exec sed -i '' -E 's/[[:space:]]+$//' {} +
*	Introduce NotesVerbosity defining verbosity levels	Adam Strzelecki	2015-07-03	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	This solves two issues: 1. Some notes were enabled explicitly for some verbosity levels, so --hintName:on has no effect if verbosity level was too low. 2. Verbosity level for notes is not longer scattered across the source code, instead if now lives in msgs.nim NotesVerbosity array 3. Individual note settings have stronger effect than verbosity setting, so --hintName:off will disable hint regardless of high verbosity setting, and vice-versa --hintName:on will enable hint even on low verbosity setting.
*	Fix typos	Federico Ceratto	2015-02-15	1	-1/+1
\|
*	VM supports math and a few os procs	Araq	2014-08-30	1	-1/+1
\|
*	renamed babelcmd to nimblecmd; config files are now nim.cfg; other renamings	Araq	2014-08-29	1	-0/+90

" Highlighting literate directives in C++ sources. function! HighlightTangledFile() " Tangled comments only make sense in the sources and are stripped out of " the generated .cc file. They're highlighted same as regular comments. syntax match tangledComment /\/\/:.*/ | highlight link tangledComment Comment syntax match tangledSalientComment /\/\/::.*/ | highlight link tangledSalientComment SalientComment set comments-=:// set comments-=n:// set comments+=n://:,n:// " Inside tangle scenarios. syntax region tangleDirective start=+:(+ skip=+".*"+ end=+)+ highlight link tangleDirective Delimiter syntax match traceContains /^+.*/ highlight traceContains ctermfg=darkgreen syntax match traceAbsent /^-.*/ highlight traceAbsent ctermfg=darkred syntax match tangleScenarioSetup /^\s*% .*/ | highlight link tangleScenarioSetup SpecialChar " Our C++ files can have mu code in scenarios, so highlight mu comments like " regular comments. syntax match muComment /# .*$/ | highlight link muComment Comment syntax match muSalientComment /##.*$/ | highlight link muSalientComment SalientComment syntax match muCommentedCode /#? .*$/ | highlight link muCommentedCode CommentedCode set comments+=n:# " Some other bare-bones mu highlighting. syntax match muLiteral %[^ ]\+:literal/[^ ,]*\|[^ ]\+:literal\>% syntax match muLiteral %[^ ]\+:label/[^ ,]*\|[^ ]\+:label\>% syntax match muLiteral %[^ ]\+:type/[^ ,]*\|[^ ]\+:type\>% syntax match muLiteral %[^ ]\+:offset/[^ ,]*\|[^ ]\+:offset\>% syntax match muLiteral %[^ ]\+:variant/[^ ,]*\|[^ ]\+:variant\>% highlight link muLiteral Constant syntax match muAssign " <- \|\<raw\>" | highlight link muAssign SpecialChar syntax match muGlobal %[^ ]\+:global/[^ ,]*\|[^ ]\+:global\>% | highlight link muGlobal SpecialChar " common keywords syntax match muRecipe "^recipe\>\|^recipe!\>\|^def\>\|^def!\>\|^before\>\|^after\>\| -> " | highlight muRecipe ctermfg=208 syntax match muScenario "^scenario\>" | highlight muScenario ctermfg=34 syntax match muPendingScenario "^pending-scenario\>" | highlight link muPendingScenario SpecialChar syntax match muData "^type\>\|^container\>\|^exclusive-container\>" | highlight muData ctermfg=226 endfunction call HighlightTangledFile() autocmd BufRead,BufNewFile *.mu set ft=mu autocmd BufRead,BufNewFile [0-9]* call HighlightTangledFile() " Scenarios considered: " opening or starting vim with a new or existing file without an extension (should interpret as C++) " opening or starting vim with a new or existing file with a .mu extension " starting vim or opening a buffer without a file name (ok to do nothing) " opening a second file in a new or existing window (shouldn't mess up existing highlighting) " reloading an existing file (shouldn't mess up existing highlighting)