It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

There are 2 constructors for Vertices, the second one Vertices.raw was left unmodified leading to similar issues as before if developers are targeting the typed list version of the constructor. @MasahideMori-SimpleAppli

Hi @flar,
I just checked about Vertices.raw documentation. Indeed, the documentation seems to have room for improvement.
However, I've never used that constructor, so I don't know how it works. If I have time, I'll dig into it and make new fixes.
Thank you.

@MasahideMori-SimpleAppli it's the same data, just packed into a few raw typed data lists that can be shared directly with the native implementation. the constructor you documented simply converts its Dart lists into typed arrays before it calls to the native init method whereas the raw constructor can dive directly into the native init.

It's easier for developers to work with dart List objects of flutter classes then the typed lists of basic numerical values, but the latter is faster for getting the data down to C++ for handing off to Skia.

Hi @flar,
Thank you for the detailed information on the constructor.
I understand. Thank you for teaching me!