So, problem solved!!
The Yoga library uses C float NaN for control flow and as function
parameters. The bindings (parts created with C-for-Go, and merged with some
other parts I found) defined a totally scrappy Undefined constant.
Setting this constant to math32.NaN() solved the problem.
--
Y
Well, it's a huge code-base, so I need to figure out how to nail it down to
something manageable. What are the interesting parts? Maybe I can provide
some more information pretty easily.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsub
data
as direct as possible. The functions prints the output as in my previous
post.
Ian Lance Taylor schrieb am Dienstag, 2. Februar 2021 um 00:58:01 UTC+1:
> On Mon, Feb 1, 2021 at 1:52 PM Robert M. Münch
> wrote:
> >
> > I know all about the problems of FP comparison, and yes I
oat
> values
> are almost equal
> ASSERT_DOUBLE_EQ(val1, val2); EXPECT_DOUBLE_EQ(val1, val2);the two
> double values are almost equal
>
> By "almost equal" we mean the values are within 4 ULP's from each other.
>
> What does testify do?
>
> Peter
I have a C library with some test-cases (using googletest) that all pass. I
created Go bindings for the C lib and converted the tests to testify format.
Some Go test fails because a return value from the C function (type float)
is different than expected. For example:
ASSERT_FLOAT_EQ(10, GetHei
