Paint is unique in that we don't have a higher level API that wraps it. Pretty much all custom painter/painting code in Flutter will directly create and manipulate paint objects. For this case in particular I don't think its unreasonable to add convienence API to it.

Oh shoot I had a VM implementation and I think I just didn't add it to the PR. Next week 😄

We don't have higher level APIs wrapping Rect or Offset either, and those don't have these kind of convenience constructors.

My bigger concern is what to do about some of the mutable fields on paint if we adopt this. I think that however we try to document it, it will be counterintuitive ... and I'm really not sure why we'd support this kind of API when it's so easy for a user who wants the simple case to work to do the right thing themselves.

We do, OTOH, have Path.from, and that is documented as doing some CoW behavior.

We clearly don't need a Rect.from or Offset.from, those are very simple classes. But Paint is a big old bag of properties. IIRC the filters objects stored on Paint are actually immutable so we don't need to deeply copy

Updated with the missing code for lib/ui/painting.dart and tests.

I'll note I'm still unable to run or debug the web tests, I've reached out for help.

A convenience method makes a lot of sense here:

1. A user that wants to copy is going to have to implement it themselves
2. We can do better than the user, because we know the internal data structure
3. Every field, AFAICT, is deeply immutable, so the operation is very low-complexity:

Paint.from(Paint other) {
  _data.buffer.asUint32List().setAll(0, other._data.buffer.asUint32List());
  _objects = other._objects?.toList();
}

Rect and Offset are simple immutable classes, where-as Paint is more complicated.

@eyebrowsoffire Jackson, the web failure (that I can't reproduce locally) only happens on chrome-dart2wasm-skwasm-ui - is there anything about this configuration that would cause hangs?

This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold.

@eyebrowsoffire I'll need some help debugging why the WASM implementation hits an infinite loop. I setup a few minutes this Friday to pair if that's more helpful, thanks!

@eyebrowsoffire I'll need some help debugging why the WASM implementation hits an infinite loop. I setup a few minutes this Friday to pair if that's more helpful, thanks!

Might be easy - @eyebrowsoffire let me know there was an issue with storkeMiterLimit not being hooked up as expected, which recently got fixed. I am re-running rebased on CI to see if true :)

Yup that did it, all tests passing!