clojusc / results Goto Github PK

Do a bunch of nested checks.

Then show the same thing using this library.

Once #3 is done, we can simply update the returned hashmap with a call to collect-values.

This should highlight the philosophy of a data-centric, message-passing approach. Keep it brief.

Then do the background.

See https://doc.rust-lang.org/std/result/

• Protocol should define:
  • exception - ex
  • stacktrace - from (.getStackTrace ex)
  • exception-type - from (type ex)
  • suppressed - from (.getSuppressed ex)
  • cause - from (.getCause ex)
• Implementation should use getter and setter in util ns for adding these to and returning them from metadata
• Constructor should take as a single arg an exception and create a map with key :msg and value (ex-message ex), then call the exception error methods defined above to set ex in the metadata. All other methods can use ex from the metadata for their impls.

Note that not all errors have to be exceptions; the Error constructor, setter, and getter should account for this.

This can be done by passing an opts hashmap to the constructor.

Multi-arity macros are supported in Clojure, but can be a bit awkward. Probably want to use a helper function here ... (see https://stackoverflow.com/a/25569059)

Show collecting results and errors when querying multiple services. Error messages can show which service they come from ...

Create an examples directory showing usage with core.async.