Check if the right number of parameters is passed into `query` about rusqlite HOT 2 CLOSED

I'd be fine with adding a message to the assert, but query should not return a Result in this case. Passing in a slice with the wrong length is a programmer error and cannot be recovered from - it's a bug that needs to be fixed.

SqliteError should only have errors from the sqlite bindings, because this library only exists to provide sqlite bindings. :) The few times we've needed to construct one, there's been a reasonable choice to make it look like a SQLite error (e.g., using SQLITE_MISUSE if we can't convert a path to a C string).

from rusqlite.

Makes sense. Having a descriptive error message in the assert should be good enough so people don't have to dig into the code to see what assert failed. You should probably double check any other asserts you have too.

from rusqlite.