As the parameter for boost was actually written as "word" in the doc string, it was replacing the previous type for word with the type intended for boost and not showing any type for boost, thus messing up what displayed on https://deepspeech.readthedocs.io/en/master/Python-API.html
* enable hot-word boosting
* more consistent ordering of CLI arguments
* progress on review
* use map instead of set for hot-words, move string logic to client.cc
* typo bug
* pointer things?
* use map for hotwords, better string splitting
* add the boost, not multiply
* cleaning up
* cleaning whitespace
* remove <set> inclusion
* change typo set-->map
* rename boost_coefficient to boost
X-DeepSpeech: NOBUILD
* add hot_words to python bindings
* missing hot_words
* include map in swigwrapper.i
* add Map template to swigwrapper.i
* emacs intermediate file
* map things
* map-->unordered_map
* typu
* typu
* use dict() not None
* error out if hot_words without scorer
* two new functions: remove hot-word and clear all hot-words
* starting to work on better error messages
X-DeepSpeech: NOBUILD
* better error handling + .Net ERR codes
* allow for negative boosts:)
* adding TC test for hot-words
* add hot-words to python client, make TC test hot-words everywhere
* only run TC tests for C++ and Python
* fully expose API in python bindings
* expose API in Java (thanks spectie!)
* expose API in dotnet (thanks spectie!)
* expose API in javascript (thanks spectie!)
* java lol
* typo in javascript
* commenting
* java error codes from swig
* java docs from SWIG
* java and dotnet issues
* add hotword test to android tests
* dotnet fixes from carlos
* add DS_BINARY_PREFIX to tc-asserts.sh for hotwords command
* make sure lm is on android for hotword test
* path to android model + nit
* path
* path
