Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | pasto | 2012-11-02 | |
| | |||
* | give <&&> and <||> same fixity as && and || | 2012-11-02 | |
| | | | | | | Suggestion by Daniel Trstenjak These are not currently mixed in my code base, so no real change. | ||
* | look for sysctl in some common sbin locations when it's not in PATH | 2012-10-06 | |
| | |||
* | noop | 2012-04-21 | |
| | |||
* | fun with symbols | 2012-03-17 | |
| | | | | | | Nothing at all on hackage is using <&&> or <||>. (Also, <&&> should short-circuit on failure.) | ||
* | optimize monadic || | 2012-03-16 | |
| | | | | | (||) used applicative style runs both conditions rather than short circuiting. Add an orM that properly short-circuits. | ||
* | added ifM and nuked 11 lines of code | 2012-03-14 | |
| | | | | no behavior changes | ||
* | treak | 2012-01-21 | |
| | |||
* | typo | 2012-01-03 | |
| | |||
* | after is a better name for observe_ | 2012-01-03 | |
| | |||
* | factor observe_ | 2012-01-03 | |
| | |||
* | add a new useful thing | 2012-01-02 | |
| | |||
* | refactor | 2011-12-03 | |
| | |||
* | broke up Utility | 2011-10-16 | |