These are chat archives for CommBank/maestro
Plusinstance, though. Also, seeing as we have filter in
Executionusing a dummy failure anyway, I wonder if we might as well just use a dummy failure in the
Hdfsmonad should have been designed so it could be an instance of these extra typeclasses. But I think you can make it an instance of
Pluswithout any problems.
Plusto result CommBank/omnitool#13
Plushas apart from the fact that we can use it to say some type must have an instance of
<+>is soo much better than
|||, I have no idea what that means. But
<+>is so obvious
Functioninstances that people might need (e.g. date time conversions), so that they tend to pass those functions in and re-use the same classes all the time
Fields, though, which users can technically do at the moment. But still a nice idea ...
Fields, if I could. But I wouldn't do away with the concept that you have a first class thing that represents a field in a datastructure, and you can pass it around, and create lists of fields, and filter them by their various properties, and so forth
Execution.fromlooked a bit more complicated, so instead I’ve moved the
ifto the end, and have it comparing the
viewHive. I’ve also rebased and squashed into a single commit that includes adding
CustomerJob.scala(linked to from the README) and
CustomerJobSpec.scala. Maybe have a quick look when you get a chance, then I’ll push the commit to master.