Gavin King
Gavin King
I'm very surprised that this isn't working already.
Right, this behavior is what is defined by the language specification. However, I agree that it *does* violate the expectation that one can change between default constructors and initializers without...
I've pushed in initial implementation of this idea to the branch `7353` and it appears to work well. The actual implementation was pretty straightforward. The question I have is whether...
Also, I'm concerned about the error message for something like this: ```ceylon "hello".map((c)=>Integer.format(c, 16)) ``` Which now works out as: > argument must be assignable to parameter 'collecting' of 'map'...
I realized that we can also do some good stuff with some operator expressions, for example: ```ceylon Float(Float) f = (x) => x/2.0; Boolean(Float) g = (x) => x>2.0; Boolean(Boolean,Boolean)...
And now it's also aware of use in boolean conditions, for example: ```ceylon Integer(Boolean) toInt = (b) => if (b) then 1 else -1; ```
I now also take into account specifier statements and value initializers.
@someth2say > Why shouldn't both be accepted? Well it's now a bad example, since I implemented inference from usages in operators like `n+100`, meaning that both of the examples are...
@fwgreen > Amazing work, as usual, but I've bumped into a problem while trying out this branch. > > ```Ceylon > Integer(String) howLongIs = (s) => s.size; > ``` >...