Elliott Stoneham
Elliott Stoneham
This would also be a great first working example of integrating a go2hx'd Go library into a Haxe project.
It would also serve to prove that Go standard library code for `bytes`, `strings` and `unicode` are fully working. Haxe test code: ``` package; import github_com.kylelemons.godebug.diff.Diff; function main():Void { trace(diff("abc\nsame\n",...
It would really help me, and other future users, if the standard library was routinely recompiled before each update to the 'nightly' version of the code.
Excellent idea to only re-go2hx the std library packages that fail their tests.
...but surely after re-go2hx-ing the failing libraries, it would be sensible to re-test the new versions to see if they now pass.
The accuracy required also depends on where the result of the calculation is being put. For example if the result of int8 + int32 is to be stored in an...
Yes, you are right @PXshadow, this is why Go always requires explicit type conversions.
@Chloe-cdq, you will need `haxe` command arguments (easier in a `.hxml` file) something like: ``` ${HAXE_LIBCACHE}/go2hx.hxml -cp golibs --main command_line_arguments.Main --cpp ``` @PXshadow is doing a great job developing this...
You're welcome, it's great to have someone take an interest in the project @Chloe-cdq. Go famously has a significant level of runtime code which has to be emulated, but hopefully...
The good news @Chloe-cdq, is that you can import Go packages ... the bad news is that almost all of the Go packages you might want to import do not...