summary refs log tree commit diff stats
path: root/compiler/vmgen.nim
Commit message (Collapse)AuthorAgeFilesLines
* make vmgen more robust in the context of 'nim check'Araq2016-12-311-2/+3
|
* removed tyArrayConstr completely from the compiler; introduced tyAlias ↵Araq2016-11-141-1/+1
| | | | instead in preparation for further bugfixes
* fixes #4915andri lim2016-10-271-1/+1
|
* fixes regressionAndreas Rumpf2016-08-261-1/+1
|
* remove unused stuffJacek Sieka2016-08-091-14/+0
|
* attempt to fix #4065Andreas Rumpf2016-08-041-2/+1
|
* compiler almost free of deprecated expr/stmt namesAndreas Rumpf2016-07-301-2/+2
|
* stdlib and compiler don't use .immediate anymoreAndreas Rumpf2016-07-291-2/+2
|
* added system.newSeqOfCap for improved efficiencyAndreas Rumpf2016-07-151-2/+14
|
* fixes #2730Andreas Rumpf2016-07-131-2/+2
|
* fixes #4462Andreas Rumpf2016-07-081-3/+5
|
* fixes #4371Andreas Rumpf2016-07-081-1/+1
|
* Merge branch 'devel' of github.com:nim-lang/Nim into develAndreas Rumpf2016-07-061-1/+4
|\
| * Fixed vm codegen for a call with compile-time args. Fixes #4412.Yuriy Glukhov2016-07-061-1/+4
| |
* | fixes #537Andreas Rumpf2016-07-061-10/+16
|/
* system. for cstrings uses value comparisons, not reference comparisonsAndreas Rumpf2016-06-021-2/+2
|
* fixes #1713Andreas Rumpf2016-05-301-4/+8
|
* Merge pull request #4113 from jcosborn/gettypeinstAndreas Rumpf2016-05-281-1/+6
|\ | | | | getTypeInst
| * getTypeInst and getTypeImpl mostly working now and added testJames Osborn2016-05-041-1/+2
| |
| * added getTypeInst which includes generic parametersJames Osborn2016-05-041-1/+5
| |
* | fixes #3956Andreas Rumpf2016-05-111-4/+5
|/
* fixes #3731Andreas Rumpf2016-04-041-3/+11
|
* fixes #3561, fixes #2409Andreas Rumpf2016-04-041-3/+7
|
* fixes #3804Andreas Rumpf2016-04-041-0/+4
|
* fixes #3973Andreas Rumpf2016-04-031-1/+1
|
* fixes #3916Andreas Rumpf2016-02-291-4/+4
|
* Fixed deprecation warnings while Nim compiles.Hans Raaf2016-01-181-1/+1
| | | | | I just removed unsigned and changed a writeLn() call to writeLine() to avoid the remaining deprecation warnings.
* first implementation of the new lambda-lifting pass; barely anything worksAndreas Rumpf2015-12-261-2/+2
|
* os.walkDir is available at compile timeAraq2015-11-101-2/+4
|
* fixes #3299Araq2015-10-151-0/+22
|
* fixes #2473; cleanup of some testsAraq2015-09-301-6/+9
|
* fixes #3387Araq2015-09-291-1/+0
|
* fixes #3357Araq2015-09-231-2/+5
|
* VM produces objects.Yuriy Glukhov2015-09-051-2/+6
|
* when nimvm stmt proof of conceptYuriy Glukhov2015-09-041-1/+4
|
* implemented macros.getImplAraq2015-08-211-0/+1
|
* VM: repl supports global variables properly"Araq2015-08-161-3/+3
|
* Merge pull request #3177 from zah/generic-types-in-macrosAndreas Rumpf2015-08-141-2/+23
|\ | | | | Generic types in macros
| * Disable the new generic params handling for immediate template and macrosZahary Karadjov2015-08-021-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since immediate templates are not subjected to the standard sigmatching algorithm, they will have a number of deficiencies when it comes to generic params: Type dependencies between the parameters won't be honoured and the bound generic symbols won't be resolvable within their bodies. We could try to fix this, but it may be wiser to just deprecate immediate templates and macros now that we have working untyped parameters. Disabling the new features is admittedly not the greatest way to handle this situations as it introduces inconsistency in the language, but at least it makes the code backwards-compatible with the previous version of the compiler instead of triggering more serious problems.
| * fix #1858 again; restores the support for static macro paramsZahary Karadjov2015-08-021-2/+19
| |
* | fixes #3066Araq2015-08-091-0/+3
| |
* | fixes #1329Araq2015-08-091-0/+2
|/
* emerald project has a chance of workingAraq2015-08-021-9/+18
|
* staticExec now supports cachingAraq2015-07-151-1/+13
|
* macros: Introduce sameType(a, b) for node typesAdam Strzelecki2015-07-031-0/+1
| | | | | | | | | | | | | Previously introduced node comparison `==` was working somehow wrong on nodes returned from getType(a), comparing just ids of the symbols. Recently introduced `==` change 47dce2688633fad840a2f5e4073c531f1cd640ca started comparing symbol nodes pointer-wise, thus strictly. Since getType(a) always creates new symbol pointing to the type, comparing two such nodes using `==` always returns false, even they point to the same type. That is why we need a new sameType macro to be able to tell if these nodes point to the same type.
* fixes #3041Araq2015-07-021-20/+26
|
* fixes #2297, fixes #2946Araq2015-06-181-6/+1
|
* Removed magics: mAbsI64rku2015-06-101-1/+1
|
* Removed magics: mBitnotI64rku2015-06-101-1/+1
|
* Removed magics: mEqI64 mLtI64 mLeI64rku2015-06-101-3/+3
|