What to do with error handling?

[matsen]

What to do with error handling?

[matsen]

Hm, naked exceptions don't get nicely printed unless you use one of the std::exception subclasses.

You can get a line number using a backtrace:

#6  0x000055555555b91f in sbn_ParseFile (inst=0x555555789c20, fname=0x55555556b228 "data/four_taxon.tre") at _build/libsbn.cpp:13

I don't want to have to ask users to do this to get detailed information on their errors. Perhaps a better solution is to use a compiler macro like so.

[matsen]

Also, am I mostly going to be using asserts? If so, should they be the doctest asserts?

[matsen]

Going to use exceptions. When we make the switch, don't forget to drop the corresponding iostream includes.

[matsen]

Can we have the messages available in Jupyter?

[christiaanjs]

Pybind documentation on redirecting std::cerr and std::cout to Python: https://pybind11.readthedocs.io/en/stable/advanced/pycpp/utilities.html#capturing-standard-output-from-ostream

[matsen]

Closed by 93cf7b6