You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The set of benchmarks in the LuaJIT-test-cleanup project are quite extensive but they lack a decent driver and timing methodology, which makes them kinda useless. This project has a good driver but not as many tests as LuaJIT-test-cleanup.
Given that LuaJIT-test-cleanup is eventually supposed to be integrated into LuaJIT proper, would you be opposed to me using your driver and related methodologies in the LuaJIT-test-cleanup and eventually in the LuaJIT project? I'll obviously give you full credit for both and retain licenses, etc.
I understand that this may never actually make it into the official repo but I'd like to give it a shot anyway, in the interest of making some forward progress in the project.
The text was updated successfully, but these errors were encountered:
Hi, thank you for the PR, I will go over it in a couple of days.
You are more than welcome to use it as you see fit.
I might actually add LuaJIT-test-cleanup as a dependency too.
The set of benchmarks in the LuaJIT-test-cleanup project are quite extensive but they lack a decent driver and timing methodology, which makes them kinda useless. This project has a good driver but not as many tests as LuaJIT-test-cleanup.
Given that LuaJIT-test-cleanup is eventually supposed to be integrated into LuaJIT proper, would you be opposed to me using your driver and related methodologies in the LuaJIT-test-cleanup and eventually in the LuaJIT project? I'll obviously give you full credit for both and retain licenses, etc.
I understand that this may never actually make it into the official repo but I'd like to give it a shot anyway, in the interest of making some forward progress in the project.
The text was updated successfully, but these errors were encountered: