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
Instead of use a command to change imports before build, using a build tag to generate the correct binary.
This will allow applications to compile enry using oniguruma with less troubles.
Signed-off-by: Antonio Jesus Navarro Perez <[email protected]>
Currently we don't have any procedure established to automatically detect changes in the linguist project and regenerate the code.
165
+
Currently we don't have any procedure established to automatically detect changes in the linguist project and regenerate the code.
166
166
So we update the generated code as needed, without any specific criteria.
167
167
168
168
If you want to update *enry* because of changes in linguist, you can run the *go
@@ -217,7 +217,7 @@ If you want to reproduce the same benchmarks you can run:
217
217
218
218
benchmarks/run.sh
219
219
220
-
from the root's project directory and it'll run benchmarks for enry and linguist, parse the output, create csv files and create a histogram (you must have installed [gnuplot](http://gnuplot.info) in your system to get the histogram).
220
+
from the root's project directory and it'll run benchmarks for enry and linguist, parse the output, create csv files and create a histogram (you must have installed [gnuplot](http://gnuplot.info) in your system to get the histogram).
221
221
222
222
This can take some time, so to run local benchmarks for a quick check you can either:
0 commit comments