Value.Int should work with int32

[pravic]

This applies to:

• Value.Int() int32
• Value.SetInt(int32)

fixes #286

cc @AshfordN

[pravic]

That was intense.

[pravic]

@AshfordN Do you have any idea why it fails in AppVeyor?

go-sciter/examples/handlers/handlers.go

Lines 28 to 31 in 73bd385

	sum := int32(0)
	for i := 0; i < len(args); i++ {
	sum += args[i].Int()
	}

invalid operation: sum += args[i].Int() (mismatched types int32 and int)

[AshfordN]

Based on my tests, this is caused by trying to build the example(s) in this (value-int32) branch while linking against the current master branch. Now I'm not at all experienced with AppVeyor, but right around line 99 of the output, just before the examples are built, it seems as though the service is pulling in go-sciter from the master branch.
Keep in mind that this PR introduces breaking changes.

[pravic]

it seems as though the service is pulling in go-sciter from the master branch.

Apparently, so.

Keep in mind that this PR introduces breaking changes.

Yeah. I wonder whether we should introduce versioning finally.

[AshfordN]

Yeah. I wonder whether we should introduce versioning finally.

I think it makes sense, especially since this touches, what I consider to be, a core part of the package. This is likely to affect a lot of code bases.

[AshfordN]

What is the status of the PR? As far as I see, this is a working branch. The only thing left to do, is to introduce versioning to avoid conflicts with existing code bases. Additionally, since versioning is now required starting with Go 1.16, I think now is a good time to implement it going forward.

[pravic]

The only thing left to do, is to introduce versioning to avoid conflicts with existing code bases.

Yep, this. Would you consider filing a PR for versioning?

[AshfordN]

No problem. I'll address it as soon as I can.