Add support for declaring static field in mapped type

Elements
1

We know currently mapped type disallow declaring static (and non-static) fields. So I have to write code as below to bypass it:

public __mapped class TestClass => object {
    public static object staticProperty => TestClassImpl.staticField;
}

public static class TestClassImpl{
    public static object staticField = new object();
}

But for static fields, it seems very easy to add support technically. Do you think it’s appropriate?

2

Thanks, logged as bugs://75644

3

Why is this mapped and not just a class? Ie could be a plain class with inline members?

4

My actual case is I have made a mapped class to MotionEvent in Android. There’s an advanced point method to get the location relative to view’s parent:

public __mapped class TouchArg => MotionEvent {

    public double[] point(int index = 0) {
        new double[] {__mapped.getX(index), __mapped.getY(index)};
    }

    public double[] point(Layout relativeToParent, int index = 0) {
        var p = point(index);
        LayoutHelper.mapPointAscend(p, TouchArgImpl.currentView, relativeToParent);
        return p;
    }
}

internal static class TouchArgImpl {
    public static Layout currentView;
}

My framework will ensure the currentView is always valid during outer code accessing that TouchArg. So the outer code has no need to pass this known parameter mannually. This also benefits other API designs.

5

oke. that makes more sense.

6

bugs://75644 got closed with status fixed.

7

Logged as bugs://i63608.

8

bugs://i63608 was closed as fixed.