Algorithms/go-perfbook
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

academic code is frequently just POC with poor performance characteristics

Browse Source
This commit is contained in:
Damian Gryski 2018-03-16 09:11:55 -07:00
parent 46114b3f97
commit c91a16f34d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
performance.md
View File

@ -1024,7 +1024,7 @@ first paper you find.
* Some papers release reference source code which you can compare against, but * Some papers release reference source code which you can compare against, but
1) academic code is almost universally terrible 1) academic code is almost universally terrible
2) beware licensing restrictions ("research purposes only") 2) beware licensing restrictions ("research purposes only")
3) beware bugs; edge cases, error checking, etc 3) beware bugs; edge cases, error checking, performance etc.
Also look out for other implementations on GitHub: they may have the same (or different!) bugs as yours. Also look out for other implementations on GitHub: they may have the same (or different!) bugs as yours.