One of the current things I'm working on is a refactored, somewhat less overpowered version of availability checks. While doing this, I've realised that:
most availability checks fall into a small amount of bins: 'always', 'has at least one thread', 'can construct paths with this filter';
many readmes describe these availability checks.
I'm wondering if it would be a good idea to defunctionalise availability checks, turning them into an enum of the form
type t =
| Always
| Has_threads
| Filter_constructible of Path_filter.t
(* | Custom of (Context.t -> bool Or_error.t) *)
This would then support writing a to_string method that auto-describes the availability check, which we can put into the action table listing.
This is a minor point, so would be somewhat back burner, but I'm just issuing an issue so I don't forget about it.
One of the current things I'm working on is a refactored, somewhat less overpowered version of availability checks. While doing this, I've realised that:
I'm wondering if it would be a good idea to defunctionalise availability checks, turning them into an enum of the form
This would then support writing a
to_stringmethod that auto-describes the availability check, which we can put into the action table listing.This is a minor point, so would be somewhat back burner, but I'm just issuing an issue so I don't forget about it.