Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | fix affecting templates with explicit generic params | Zahary Karadjov | 2017-05-13 | 4 | -30/+23 |
| | |||||
* | fix tinvalidinout | Zahary Karadjov | 2017-05-13 | 2 | -7/+4 |
| | |||||
* | attempt to fix a compilation problem caused by nimcache | Zahary Karadjov | 2017-05-13 | 1 | -0/+0 |
| | |||||
* | work-around for defining imported types with weak covariance | Zahary Karadjov | 2017-05-13 | 2 | -4/+23 |
| | |||||
* | enforce the covariance rules for user-defined generic types | Zahary Karadjov | 2017-05-13 | 5 | -17/+105 |
| | |||||
* | manual additions for the covariant generic parameters | Zahary Karadjov | 2017-05-12 | 1 | -2/+87 |
| | |||||
* | explain covariance in the manual | Zahary Karadjov | 2017-05-12 | 1 | -0/+16 |
| | |||||
* | covariance for arrays and sequences | Zahary Karadjov | 2017-05-12 | 3 | -48/+245 |
| | |||||
* | doh, forgot to add all files in the previous commit | Zahary Karadjov | 2017-05-12 | 4 | -15/+65 |
| | |||||
* | covariance for generic importc types | Zahary Karadjov | 2017-05-12 | 1 | -0/+253 |
| | |||||
* | support for external types with covariant generic params | Zahary Karadjov | 2017-05-08 | 8 | -3/+62 |
| | |||||
* | fix 5756 | Zahary Karadjov | 2017-04-30 | 2 | -1/+40 |
| | |||||
* | close #5757 | Zahary Karadjov | 2017-04-30 | 2 | -3/+23 |
| | |||||
* | close #5726 | Zahary Karadjov | 2017-04-28 | 1 | -2/+4 |
| | | | | | | | | | | | | Turned out that the old code was wrong. I'm not sure why it used to work. `response.body` properly resolves to an async proc defined in the httpclient module with the following signature: proc body*(response: AsyncResponse): Future[string] {.async.} Perhaps the old code was somehow matching the body field of the `AsyncResponse` object, which is marked as private. | ||||
* | hold back the new | operator for types as it creates mysterious problems fro ↵ | Zahary Karadjov | 2017-04-28 | 1 | -3/+0 |
| | | | | tests/trmacros/tor | ||||
* | alternative fake covariance based on converters | Zahary Karadjov | 2017-04-28 | 2 | -3/+25 |
| | |||||
* | more advanced fake covariance | Zahary Karadjov | 2017-04-28 | 1 | -3/+48 |
| | |||||
* | a simple way to simulate covariance in generic types | Zahary Karadjov | 2017-04-28 | 2 | -1/+17 |
| | |||||
* | Allow tyOr,tyAnd and tyNot to be constructed in more contexts | Zahary Karadjov | 2017-04-28 | 3 | -18/+53 |
| | |||||
* | fix a regrsesion in signature matching of derived ptr types | Zahary Karadjov | 2017-04-18 | 2 | -3/+25 |
| | |||||
* | Restore the compilation of linalg by tweaking the complex disambiguation rules | Zahary Karadjov | 2017-04-16 | 1 | -10/+18 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit is a potentially breaking change, but the problem was that linalg was relying on a previous bug in the compiler, which was fixed in the concepts branch. With the old disambiguation rules, generic procs like: proc \`==\`[T](lhs, rhs: T) and proc \`==\`(lhs, rhs: Matrix32|Matrix64) .. were considered equal, even though it's obvious that the second one should be preferred. We never noticed this, because there was a bug in sigmatch incorrectly counting one of the params of the second proc as a non-generic match, thus giving it an edge. This commit gives some preference to tyOr and tyAnd during the complex disambiguation, which may affect overload resolution in other cases. I see this only as a temporary solution. With my upcoming work on concept refinement, I plan to provide an experimental implementation of alaternative C++-like rules for determining which proc is more specific. We can then discuss our strategy for dealing with such a breaking change. | ||||
* | fix regression in tmatrixconcept | Zahary Karadjov | 2017-04-16 | 1 | -0/+4 |
| | |||||
* | more sophisticated test for the previous commit | Zahary Karadjov | 2017-04-16 | 1 | -2/+22 |
| | |||||
* | fix compilation regression in alea | Zahary Karadjov | 2017-04-16 | 4 | -12/+37 |
| | |||||
* | fix a compilation error in linalg | Zahary Karadjov | 2017-04-16 | 2 | -25/+39 |
| | |||||
* | fix #5689 | Zahary Karadjov | 2017-04-15 | 4 | -11/+82 |
| | |||||
* | fix #5683 | Zahary Karadjov | 2017-04-14 | 3 | -6/+25 |
| | |||||
* | fix a parsing regression (do is still mandatory in some situations) | Zahary Karadjov | 2017-04-14 | 2 | -1/+20 |
| | |||||
* | allow StmtLists to pass through semExprWithType | Zahary Karadjov | 2017-04-11 | 2 | -5/+8 |
| | | | | | | This fix was necessary in order to fix the lambda lifting used in the "jsffi" module, which relies on turning nkStmtList into nkLambda in a catch-all dot operator. | ||||
* | wip | Zahary Karadjov | 2017-04-11 | 1 | -4/+5 |
| | |||||
* | lift parameter-less do block to lambdas | Zahary Karadjov | 2017-04-10 | 10 | -26/+46 |
| | |||||
* | support post expression blocks in return and yield | Zahary Karadjov | 2017-04-10 | 2 | -3/+4 |
| | |||||
* | fix a regression in tlexerex | Zahary Karadjov | 2017-04-10 | 2 | -16/+16 |
| | |||||
* | adapt quote to the new parsing rules | Zahary Karadjov | 2017-04-10 | 1 | -8/+11 |
| | |||||
* | fix a parsing regression (calls with do inside param lists) | Zahary Karadjov | 2017-04-10 | 2 | -2/+24 |
| | | | | | This treatment is applied only when "do" is used, because the code foo(x: bar) is recognized as object construction. | ||||
* | fully consisent parsing between the new and the old 'do blocks' | Zahary Karadjov | 2017-04-10 | 2 | -78/+545 |
| | |||||
* | the new blocks without 'do' produce compatible AST with 'do blocks' | Zahary Karadjov | 2017-04-09 | 2 | -12/+10 |
| | |||||
* | improve the usability of the jsffi module | Zahary Karadjov | 2017-04-09 | 2 | -10/+104 |
| | | | | | | * All JavaScript operators are usable with JsObject * The dot operators will use native JavaScript strings * Results returned from dot calls are consired discardable | ||||
* | fix the do notation when used with procs | Zahary Karadjov | 2017-04-09 | 7 | -11/+59 |
| | |||||
* | fix #5643; fix #5644 | Zahary Karadjov | 2017-04-08 | 4 | -7/+42 |
| | |||||
* | Restore the Nim's 0.14 proper handling of generic aliases | Zahary Karadjov | 2017-04-08 | 12 | -55/+236 |
| | | | | | | | | | | | A more efficient implementation is possible by restoring the old lifting ot tyGenericInvocation to tyGenericInst in liftTypeParam, but this fix will suffice for now. fixes #5087 fixes #5602 fixes #5641 fixes #5570 | ||||
* | test case for #5640 | Zahary Karadjov | 2017-04-07 | 1 | -0/+6 |
| | |||||
* | fix #5658 | Zahary Karadjov | 2017-04-07 | 3 | -4/+36 |
| | |||||
* | fix #5654 | Zahary Karadjov | 2017-04-07 | 3 | -2/+47 |
| | |||||
* | fix #5642 | Zahary Karadjov | 2017-04-07 | 4 | -3/+31 |
| | |||||
* | fix #5648 | Zahary Karadjov | 2017-04-07 | 2 | -2/+25 |
| | |||||
* | wip fix #5640 | Zahary Karadjov | 2017-04-07 | 2 | -1/+3 |
| | |||||
* | Implement json.`%` for enums. | Dominik Picheta | 2017-04-06 | 1 | -0/+5 |
| | |||||
* | Add some extra methods and fields to DOM module. | Dominik Picheta | 2017-04-06 | 1 | -0/+11 |
| | |||||
* | Merge pull request #5564 from nim-lang/fix/4556 | zah | 2017-04-06 | 9 | -76/+455 |
|\ | | | | | Fix/4556 |