Martin R. Albrecht
Martin R. Albrecht
Heya, take a look at e.g. https://bitbucket.org/malb/m4ri/src/a1af290b8e9757142daad5750bc2181be53d0d93/m4ri/brilliantrussian.h?at=master&fileviewer=file-view-default#brilliantrussian.h-207 The tag `\example` there points to a file where the function is called to give the reader some guidance of how it's used....
Mhhh, these mean nothing to me. @joerowell or @cr-marcstevens any ideas?
See https://gist.github.com/vidavidorra/548ffbcdae99d752da02 and https://groups.google.com/forum/#!topic/fplll-devel/xndGnk7Ts-o
FWIW, disabling fuzzy searching makes it work for me: ```emacs-lisp ; :fuzzy-match t ```
I just commented out the line reading `:fuzzy-match t` in the function `helm-lsp--workspace-symbol` like this: ```emacs-lisp (defun helm-lsp--workspace-symbol (workspaces name input) "Search against WORKSPACES NAME with default INPUT." (setq helm-lsp-symbols-result...
Cool! Do we have any tests that would test if those two implementations return the same output (up to numerical noise)?
Is `arora_gb` crashing here, i.e. what happens when you call `LWE.arora_gb(params)`?
If we throw a `ValueError` here do we gain anything? That is, if the user then does the right thing and produces a dense distribution, it'd still return `False` on...
I've been using it since opening the ticket, but I didn't systematically test it, so not sure if that's enough.
Yep, that's my impression, all working as expected and strings resolved.