tvgRender has been introduced as an interface similar to HAL or RHI, but This one is more of a helper function. In fact, a single function like bool genDashPath(const RenderPath& in, RenderPath& out); might be sufficient for this purpose. The question is: where would be the most appropriate place to include it...

Additionally, perhaps we can also replace the software ver. with this as well.

tvgRender has been introduced as an interface similar to HAL or RHI, but This one is more of a helper function. In fact, a single function like bool genDashPath(const RenderPath& in, RenderPath& out); might be sufficient for this purpose. The question is: where would be the most appropriate place to include it...

thats a good point and good question.
we can hide inplementation in render.cpp file and make a function as a public interface like bool genDashPath(const RenderPath& in, RenderPath& out, ...);

Additionally, perhaps we can also replace the software ver. with this as well.

As I can see dashers for gl and sw is mostly similar. The difference is in output format.
gl version: path-to-path conversion (RenderPath to RenderPath)
sw version: path-to-outline conversion (RenderPath to SwOutline)wg
wg version (current): outline-to-outline conversion (WgVertexBuffer to WgVertexBuffer, will be get rided)

@SergeyLebedkin Please consider this interface:

bool RenderShape::strokeDash(RenderPath& out) const

@SergeyLebedkin Please consider this interface:

bool RenderShape::strokeDash(RenderPath& out) const

whats do you mean consider? this dasher uses all settings for dashing

@SergeyLebedkin I suggest defining a common internal interface (strokeDash()) for the Dash Stroker. The RenderPath& out parameter could be used to return the dash path data.