Wrong calculation of path's intersection.

[pcerman]

Description

Many times SkiaSharp doesn't calculate intersection of two paths well. Result path contains no points. For example next dotNet core console application is not able to calculate intersection. It writes 0 on console.

The same example in C++ is working well. You can try it in the next fiddle record:

https://fiddle.skia.org/c/cde611c02e7cfb956670649610eb40d3

Code

    class Program
    {
        private static float SkBits2Float(uint n)
        {
            byte[] data = BitConverter.GetBytes(n);
            return BitConverter.ToSingle(data, 0);
        }

        static void Main(string[] args)
        {
            SKPath path_a = new SKPath();

            path_a.FillType = SKPathFillType.Winding;

            path_a.MoveTo(SkBits2Float(0x00000000), SkBits2Float(0x44070000));
            path_a.LineTo(SkBits2Float(0x44340000), SkBits2Float(0x44070000));
            path_a.LineTo(SkBits2Float(0x44340000), SkBits2Float(0x00000000));
            path_a.LineTo(SkBits2Float(0x00000000), SkBits2Float(0x00000000));
            path_a.Close();

            SKPath path_b = new SKPath();

            path_b.FillType = SKPathFillType.EvenOdd;

            path_b.MoveTo(SkBits2Float(0xB6D27CA9), SkBits2Float(0x44070000));
            path_b.LineTo(SkBits2Float(0x44340000), SkBits2Float(0x44070000));
            path_b.LineTo(SkBits2Float(0x44340000), SkBits2Float(0x36CCD0F6));
            path_b.LineTo(SkBits2Float(0xB6D27CA9), SkBits2Float(0x36CCD0F6));
            path_b.Close();

            SKPath path_r = path_a.Op(path_b, SKPathOp.Intersect);

            if (path_r != null)
            {
                Console.WriteLine(path_r.PointCount);
            }
        }
    }

Expected Behavior

It has to calculate intersection well as the fiddle example (result path is rendered by green color).

Basic Information

• Version with issue: SkiaSharp nuget package 1.60.3
• IDE: Visual Studio 2017 version 15.8.7
• Platform Target Frameworks: .NET Core 2.1

Example was tested on Windows 10

VS bug #738688