897854b3dc
KT-6671 Report unused constructor parameters
...
#KT-6671 fixed
2015-01-27 22:38:27 +03:00
7a5124215a
Updated test data for Array<out T> vararg type
2014-12-12 23:08:28 +03:00
5b4f10e698
Made vararg parameters have Array<out T> type
...
instead of simply Array<T>
#KT-1638 Fixed
#KT-2163 Fixed
#KT-3213 Fixed
#KT-4172 Fixed
#KT-5534 Fixed
2014-12-12 23:08:28 +03:00
75c887048e
Drop AbstractLazyResolveRecursiveComparingTest test
...
Test data from compiler/testData/lazyResolve/ was moved to diagnostics tests
2014-12-03 14:08:23 +03:00
0eee83b6ec
Lazy logs removed
2014-11-21 18:59:45 +03:00
2a83053355
Updated lazy log tests
2014-11-21 14:02:45 +03:00
b7c473f59e
Update lazy.log files
2014-11-17 17:45:01 +03:00
4f0d83a7fe
Update lazy logs after field rename
2014-11-11 18:35:39 +03:00
4892369cf4
Diagnostic tests are logging their lazy activity
2014-11-10 17:24:04 +02:00
3a8ad45dec
Append newline to EOF for .txt test data files
...
Reverts and fixes 102f0d3
2014-10-21 03:18:27 +04:00
6564231040
Descriptor test data for diagnostic tests fixed
2014-10-13 15:38:10 +04:00
e796f88b38
Regenerate test data with constructed descriptors for diagnostics tests
2014-09-18 17:58:23 +04:00
791fa22abb
KT-4405 Control-flow analysis is not performed for some local declarations #KT-4405 Fixed
2014-02-12 12:48:13 +04:00
c739632c57
report 'ambiguity' on reference, not on the whole expression
...
as other type inference errors
2013-09-03 13:09:15 +04:00
da4f1aec1d
KT-422 Tune literal typing rules so that varargs overloaded by primitive types work
...
#KT-422 fixed
2013-02-08 15:10:39 +04:00
bbde38a6dc
KT-1360 Vararg bug in front-end
2013-01-31 18:54:37 +04:00
3d8d92c7d3
JetDiagnosticsTest migrated to TestGenerator
...
- test data files renamed from *.jet to *.kt
2012-07-10 14:48:11 +04:00
789ff0b273
KT-1838 Constructor with a vararg
...
Resolution for properties declared as primary constructor parameters used to ignore the varargs annotation.
#KT-1838 Fixed
2012-04-23 14:16:07 +04:00
45a0873afa
KT-1835 cannot call a Java API which has a method from(String) and from(String...)
...
The problem was in the "more specific" relation, that didn't pay enough attention to varargs.
The correct behavior is in the spirit of JLS 15.12.2 (as of Java 5):
* a fixed-arity function always wins over a variable-arity functions
* if two vararg functions are compared, their parameters are checked for subtyping.
In the latter case, the candidates may have different number of formal parameters, so we
compare the matching parts and then check the rest against the vararg parameter.
#KT-1835 Fixed
2012-04-20 19:10:10 +04:00
0f98c281ab
KT-1781 Can't distinguish between two constructors
...
#KT-1781 Fixed
Now, if foo() and foo(vararg bar) both match the call site, the first one is preferred
2012-04-16 16:14:08 +04:00
Evgeny Gerashchenko