fee2a7ecfa
This postpones the semantic pass over the generic's body until the generic is instantiated. There are several pros and cons for this method and the capabilities that it enables may still be possible in the old framework if we teach it a few new trick. Such an attempt will follow in the next commits. pros: 1) It allows macros to be expanded during generic instantiation that will provide the body of the generic. See ``tmacrogenerics``. 2) The instantiation code is dramatically simplified. Dealing with unknown types in the generic's body pre-pass requires a lot of hacky code and error silencing in semTypeNode. See ``tgenericshardcases``. cons: 1) There is a performance penalty of roughly 5% when bootstrapping. 2) Certain errors that used to be detected in the previous pre-pass won't be detected with the new scheme until instantiation. |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| caas | ||
| ccg | ||
| compile | ||
| css | ||
| dll | ||
| gc | ||
| js | ||
| manyloc | ||
| patterns | ||
| reject | ||
| rodfiles | ||
| run | ||
| system | ||
| testdata | ||
| threads | ||
| benchmark.nim | ||
| caasdriver.nim | ||
| js.html | ||
| js.nim | ||
| mmaptest.nim | ||
| readme.txt | ||
| rectest.nim | ||
| specials.nim | ||
| stckovfl.nim | ||
| sunset.tmpl | ||
| tester.nim | ||
This directory contains the test cases. Each test must have a filename of the form: ``t*.nim`` Each test can contain a spec in a ``discard """"""`` block. The folder ``rodfiles`` contains special tests that test incremental compilation via symbol files. The folder ``dll`` contains simple DLL tests.