Irmen de Jong
|
66574d058a
|
renamed InferredType.typeOrElse to getOr()
this is closer to the convention of most functional return types
|
2021-10-13 00:21:38 +02:00 |
|
Irmen de Jong
|
f38fe092ee
|
optimized imports
|
2021-10-11 00:22:04 +02:00 |
|
Irmen de Jong
|
5db0408b9f
|
syntactic sugar: turned some functions into read only properties
|
2021-10-11 00:05:51 +02:00 |
|
Irmen de Jong
|
7241cef7a5
|
fix char range in float-range test and exclude test.p8 example from tests
|
2021-09-12 18:59:53 +02:00 |
|
Irmen de Jong
|
5145296486
|
fix test assertion for float ranges (and re-enable test)
|
2021-09-12 18:53:12 +02:00 |
|
meisl
|
1b451180c1
|
* test helpers assumeXyz (helpers/paths.kt) return the resulting path (unless they fail, of course); test directories are checked automatically at init, so no sanityCheckDirectories is needed anymore
|
2021-07-31 14:44:02 +02:00 |
|
meisl
|
522bf91c30
|
* refactor RangeExpr, step 2: make toConstantIntegerRange and size *extension methods* and move them to compiler/astprocessing/AstExtensions.kt (along with the simple helper makeRange). They are in fact *only* used from the compiler module - strong indication that they actually belong there.
|
2021-07-17 21:13:34 +02:00 |
|
meisl
|
48d3abc1fe
|
* refactor RangeExpr, step 1: remove IStringEncoding as ctor arg and instead put it as arg to the two methods that actually depend on it: toConstantIntegerRange and size (as *it* calls the former)
|
2021-07-17 20:45:17 +02:00 |
|
meisl
|
3f6f25e06f
|
* @Disable tests re unsolved #55, "float[] initializer with range and no explicit array size"
|
2021-07-17 17:12:16 +02:00 |
|
meisl
|
34ba07ee3b
|
+ expose #55: float[] initializer as range where no array size is stated
|
2021-07-17 16:30:16 +02:00 |
|