Stéphane Épardaud
Stéphane Épardaud
> Would this automagically pass the correct parent for the panes, labels and button? I suppose we could hard-code this strategy for Swing. I'd have to take a look. That's...
I suppose it can be a set of annotations, yes.
We can hard-code defaults for Android and Swing, but not for every other similar module.
> Isn't this something that could be turned into plugins? It requires changes in the model loader, model and backend. It's very pervasive. Hard to turn into a plugin :(
I've stopped working on this proto since to be useful it depends on #1617 or #6189 which are for 1.3.
Well, I didn't even know the spec allowed this. Is `I.v` defined as a `Value` or a `Function` here?
This requires changes in `ClassTransformer.transformRefinementSpecifierStatement` that are hard to write and test. IMO this is too much work to fix for 1.2.3 for too little value because it's never been...
There's no default access in interfaces: by default they're all public.
So this stops generation of the second interface because it contains _unknown types_. This is done in `DeclarationErrorVisitor#177`. You can debug the generation in `IssuesTests_7000_7499.testBug7000` on the `7000` branch.
If we are trying to make our language more in-line with its siblings, then `${}` is definitely the way to go, I'm afraid. Changing one unique syntax to an extremely...