Why is Marker not a Widget?

[DirtyNative]

What do you want implemented?

I am not that deep into the code for this package, but I wonder why the Marker class is not a Widget. It would allow us to define and styler the Widget in some other places. Just for an example:

class MyMapMarker extends StatelessWidget {
  final LatLng position;

  const MyMapMarker({
    super.key,
    required this.position,
  });

  @override
  Widget build(BuildContext context) {
    return Marker(
      width: 32,
      height: 32,
      point: position,
      child: Icon(
        Icons.pin,
        size: 32,
        color: Colors.black,
      ),
    );
  }
}

Without extending from a Widget, we need to create a class extending from Marker, and pass the child from the constructor to the Markers constructor. At least thats one way to do.
Or do I oversee something which prevents from being a Widget?

What other alternatives are available?

No response

Can you provide any other information?

No response

[JaffaKetchup]

The simple reason is history. The MarkerLayer was originally introduced in efc2585, back when things looked very different in 2018, and there were very few widgets to be found externally at all.
When we moved to widgets for layers, instead of the old 'options' objects, we didn't change the Markers themselves.

The other reason is that we layout/position the markers in the MarkerLayer, and it is somewhat easier to do it here, than doing it in each Marker's build method (if it had one).

We have no plan at the moment to change this. The child widget of the Marker can always be made your own widget, and you can just assign the marker to a variable or generator function which takes the child widget.