Magnus

See https://github.com/rusterlium/rustler/pull/538, which tackles this problem.

@kostis a new release of PropEr would be appreciated for https://github.com/alfert/propcheck/pull/226#issuecomment-2002115872 as well. Can we help with making a release happen?

Note that the `:verbose` option (https://github.com/alfert/propcheck/pull/48) also outputs the results of assertions. One can also use `PROPCHECK_VERBOSE=1` to set that option globally.

Closing in favor of https://github.com/rusterlium/rustler/pull/496.

Thanks! Can you fix clippy? Also, would be nice to see some example results, could you simply post the machine you used and the output of the benchmark here? :)...

> What about having a single Benchmark.run() that can read command line arguments and generate the benchee options? That way for local testing developers can run a single specific test...

@cleaton seems I kind make the github actions run again. Can you rebase on master so that the tests run again?

Thanks for the report. I'd like to understand your use-case a little better. You explicitly don't want to build the binary usually and use a feature to disable building it?...

If I understand your question correctly, you are wondering if you should be able to use an absolute path for `load_from` because currently it only allows a relative path?

> did I just find a bug or is there a reason as to why only relative paths are allowed? I think this might be a bug, `load_from` should IMO...